Debug tool to check the internal state of the MCP server.
AI agents call debug_context to retrieve information from LinkedIn Intelligence 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 internal state information for debugging purposes. It performs introspection/diagnostics without creating, modifying, deleting, or executing arbitrary operations. While it may expose sensitive internal details, its primary function is read-only querying of system state, placing it in the Read category.
From the tool's definition Tool name is 'debug_context' and description states it is a 'Debug tool to check the internal state of the MCP server.' The verb 'check' indicates retrieval of diagnostic information without modification or side effects.
Documented attack patterns abuse exactly the kind of access debug_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_context:
{
"version": "1",
"default": "deny",
"tools": {
"debug_context": {}
}
}debug_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Debug tool to check the internal state of the MCP server. It is categorised as a Read tool in the LinkedIn Intelligence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for debug_context: 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 LinkedIn Intelligence MCP Server. Nothing to install.
debug_context 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 debug_context 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 debug_context. 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.
debug_context is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.