Get persisted logs + screenshots + summary for any test session
AI agents call test_get_session_logs 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.
This tool retrieves and queries previously stored test session data (logs, screenshots, summaries) from persistent storage. It has no side effects, does not modify or delete data, does not execute code or commands, and does not move resources. It is a straightforward read operation that fits the 'Read' category (retrieve, query, fetch).
From the tool's definition Tool name contains 'get' and description states 'Get persisted logs + screenshots + summary' — purely retrieval of existing data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get persisted logs + screenshots + summary for any test session. 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_get_session_logs: 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_get_session_logs 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_get_session_logs 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_get_session_logs. 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_get_session_logs 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 →