Check whether the mcp-ad4m server is registered at user scope in ~/.claude.json. Detects project-scope and wrong-file registrations that cause silent failures. Run at session start to verify correct setup.
AI agents call ad4m_config_check to retrieve information from Mcp Ad4m without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and inspects configuration data (whether a server is registered in ~/.claude.json) to verify setup correctness. It performs no mutations, executes no code, and triggers no external operations. It is a read-only diagnostic check with minimal blast radius if misused by an agent.
From the tool's definition Tool description states it 'Check[s] whether the mcp-ad4m server is registered' and 'Detects project-scope and wrong-file registrations' — purely diagnostic inspection of configuration files without modification or execution.
Attacks that exploit this kind of access
Check whether the mcp-ad4m server is registered at user scope in ~/.claude.json. Detects project-scope and wrong-file registrations that cause silent failures. Run at session start to verify correct setup. It is categorised as a Read tool in the Mcp Ad4m MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ad4m MCP server in PolicyLayer and add a rule for ad4m_config_check: 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 Mcp Ad4m. Nothing to install.
ad4m_config_check 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 ad4m_config_check 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 ad4m_config_check. 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.
ad4m_config_check is provided by the Mcp Ad4m MCP server (thefranceway/mcp-ad4m). 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 →