AI agents call check_release_compatibility 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 tool retrieves and validates information about release compatibility, package metadata, and migration readiness. It has no capability to modify, delete, or execute operations—it performs inspection and validation only. Even though it may be used in a development/release context, the tool itself is fundamentally a diagnostic/read operation.
From the tool's definition Tool name 'check_release_compatibility' and description indicate it 'Check[s]' (queries/inspects) local release compatibility metadata, migrations, exports, and changelog information.
Attacks that exploit this kind of access
Check local release compatibility for package metadata, migrations, exports, Bun global install guidance, changelog readiness, and rollback steps. 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 check_release_compatibility: 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.
check_release_compatibility 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 check_release_compatibility 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 check_release_compatibility. 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.
check_release_compatibility 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 →