AI agents call get_logs to retrieve information from Rn Debug without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical log data using pagination, which is a read-only query operation with no side effects on the system or application state. It does not execute code, modify data, delete information, or perform financial operations. The low severity reflects minimal blast radius—an AI agent misusing this tool could only over-read logs, creating informational leakage but no operational harm.
From the tool's definition Tool name is 'get_logs' and description states 'Read buffered non-error logs using cursor-based pagination.' The verb 'Read' explicitly indicates retrieval without modification or side effects.
Attacks that exploit this kind of access
Read buffered non-error logs using cursor-based pagination. It is categorised as a Read tool in the Rn Debug MCP Server, which means it retrieves data without modifying state.
Register the Rn Debug MCP server in PolicyLayer and add a rule for get_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 Rn Debug. Nothing to install.
get_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 get_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 get_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.
get_logs is provided by the Rn Debug MCP server (rn-debug-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 →