Get all console logs captured during the session
AI agents call get_console_logs to retrieve information from QA Agent Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns data (console logs) with no side effects. It does not modify state, execute code, delete data, or trigger external operations. The blast radius is minimal: console logs may contain sensitive debugging information, but reading them poses only informational risk. Classification as Read is appropriate.
From the tool's definition Tool retrieves console logs captured during a session without modifying, deleting, or executing any operations. Description explicitly states 'Get all console logs' — a pure read/retrieval action.
Attacks that exploit this kind of access
Get all console logs captured during the session. It is categorised as a Read tool in the QA Agent Pro MCP Server, which means it retrieves data without modifying state.
Register the QA Agent Pro MCP server in PolicyLayer and add a rule for get_console_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 QA Agent Pro. Nothing to install.
get_console_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_console_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_console_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_console_logs is provided by the QA Agent Pro MCP server (samusilv/qa-agent-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 →