query_system_logs
AI agents call query_system_logs to retrieve information from Systems Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name strongly suggests querying (read-only retrieval) of system logs rather than modification, deletion, or execution. System log queries are non-destructive introspection. However, confidence is not higher due to empty description, which prevents direct confirmation of scope and limitations.
From the tool's definition Tool name 'query_system_logs' indicates retrieval of log data. Description is empty, but context from sibling tools (capture_system_snapshot, get_network_connections, get_process_details, health_check, list_kernel_modules, list_services) all perform…
Attacks that exploit this kind of access
query_system_logs. It is categorised as a Read tool in the Systems Manager MCP Server, which means it retrieves data without modifying state.
Register the Systems Manager MCP server in PolicyLayer and add a rule for query_system_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 Systems Manager. Nothing to install.
query_system_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 query_system_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 query_system_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.
query_system_logs is provided by the Systems Manager MCP server (knuckles-team/systems-manager). 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 →