Compare two persisted test sessions
AI agents call test_compare_sessions to retrieve information from AutoDev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and compares persisted test session data from SQLite logging mentioned in the server description. The verb 'compare' is fundamentally a read operation that analyzes existing data without side effects, creation of new data, code execution, or destructive actions. The low severity reflects that comparison of test metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'test_compare_sessions' and description 'Compare two persisted test sessions' indicate data retrieval and comparison of existing test session records with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Compare two persisted test sessions. It is categorised as a Read tool in the AutoDev MCP MCP Server, which means it retrieves data without modifying state.
Register the AutoDev MCP server in PolicyLayer and add a rule for test_compare_sessions: 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 AutoDev MCP. Nothing to install.
test_compare_sessions 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 test_compare_sessions 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 test_compare_sessions. 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.
test_compare_sessions is provided by the AutoDev MCP server (rookiejefren/autocoding-mcp). 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 →