Get system debug messages
AI agents call get_debug_messages to retrieve information from HC3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries debug messages from the HC3 system without creating, modifying, deleting, or executing any operations. It has no side effects and falls squarely within the Read category. Severity is low because debug messages are informational data with minimal security impact unless they contain sensitive credentials, but the tool itself performs no damaging operations.
From the tool's definition Tool name 'get_debug_messages' and description 'Get system debug messages' indicate retrieval of existing debug logs with no modification, deletion, or execution of commands. The verb 'Get' is explicitly read-only.
Attacks that exploit this kind of access
Get system debug messages. It is categorised as a Read tool in the HC3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for get_debug_messages: 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 HC3 MCP Server. Nothing to install.
get_debug_messages 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_debug_messages 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_debug_messages. 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_debug_messages is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_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 →