{"version":"2.1.302","anchor":"mcp-serve-gains-a-readcalls-tool-and-repo-rule-transport","canonical_anchor":"mcp-serve-gains-a-readcalls-tool-and-repo-rule-transport","heading":"claude mcp serve can report on tool calls and accept rules from the client","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/mcp-serve-gains-a-readcalls-tool-and-repo-rule-transport","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### `claude mcp serve` can report on tool calls and accept rules from the client\n\n`claude mcp serve` gains a ReadCalls tool that reports on running and finished tool calls, and clients can pass in deny and ask rules\n\n**Unclear.** Whether ReadCalls is available to every client of `claude mcp serve` or held behind a setting is not stated.\n\n**What**\n\n`claude mcp serve` runs Claude Code as an MCP server, so another program can connect to it and use its tools. A tool call is one use of a tool, such as running a command. Two things are new:\n\n- A tool named ReadCalls reports on tool calls that are running, finished or running in the background, and can be narrowed to a single call by its `tool_use_id`.\n\n- An experimental capability, `anthropic\/uploadsUnderSessionRules`, and a `repo_rules` argument let the connecting program add its own deny and ask rules, which decide what is blocked and what needs approval.\n\n**Why**\n\nA program connected to `claude mcp serve` can now check on the state of calls and attach its own permission rules.\n\n- Area: MCP\n- Names: `claude mcp serve`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}