AI agents call get_agent_reliability_scorecard to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that retrieves and aggregates existing historical data about task execution and agent performance. It has no destructive, write, execute, or financial implications. The data retrieved is purely informational for monitoring/auditing purposes.
From the tool's definition The tool description explicitly states it 'Get[s] one local-only agent reliability scorecard' from existing data (completed tasks, failed runs, verification evidence, stale locks, handoffs, retry history).
Attacks that exploit this kind of access
Get one local-only agent reliability scorecard from completed tasks, failed runs, verification evidence, stale locks, handoffs, and retry history. 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 get_agent_reliability_scorecard: 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.
get_agent_reliability_scorecard 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 get_agent_reliability_scorecard 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 get_agent_reliability_scorecard. 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.
get_agent_reliability_scorecard 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →