AI agents call get_logs_by_level to retrieve information from Console without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing log data based on severity level criteria. It is a query operation with no side effects, no code execution, and no data modification or destruction. The severity is low because log access may reveal sensitive debugging information, but the blast radius is limited to information disclosure without operational impact.
From the tool's definition Tool name 'get_logs_by_level' and description 'Get logs filtered by severity level' indicate data retrieval with filtering. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
Get logs filtered by severity level (fault, error, warning, info, debug). It is categorised as a Read tool in the Console MCP Server, which means it retrieves data without modifying state.
Register the Console MCP server in PolicyLayer and add a rule for get_logs_by_level: 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 Console. Nothing to install.
get_logs_by_level 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_by_level 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_by_level. 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_by_level is provided by the Console MCP server (rohithgoud30/console-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 →