This record as markdown: /tools/todos/resource-diagnostics.md
What resource_diagnostics does on Todos
AI agents call resource_diagnostics to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why resource_diagnostics is rated Low
The tool retrieves and displays diagnostic information about MCP resource subscriptions. The verb 'show' and the nature of diagnostics (inspection/monitoring) confirm this is a read-only operation that queries system state without modifying, deleting, or executing external operations. No side effects are implied.
From the tool's definition Tool name 'resource_diagnostics' and description 'Show MCP resource subscription diagnostics' indicate data retrieval and inspection of system state with no side effects.
Attacks that exploit this kind of access
The rule that runs resource_diagnostics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resource_diagnostics, this is the rule to start with:
resource_diagnostics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every resource_diagnostics call is checked against it from then on.
Questions about resource_diagnostics
Show MCP resource subscription diagnostics. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for resource_diagnostics: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Todos. Nothing to install.
resource_diagnostics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the resource_diagnostics rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for resource_diagnostics. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
resource_diagnostics is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
This server
Across the catalogue