AI agents call synaptex_status to retrieve information from Synaptex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The synaptex_status tool queries and reports the current state of Synaptex infrastructure without altering any data or triggering side effects. This is a read-only diagnostic tool that retrieves status metrics, making it Read category with low severity. The blast radius of misuse is minimal—an agent could only learn about system state, not manipulate it.
From the tool's definition Tool description states it retrieves status information about infrastructure components (Ollama, embed model, index, projects). No modification, deletion, or execution of external operations is described. Purely informational.
Attacks that exploit this kind of access
Synaptex infrastructure status: Ollama, embed model, index, projects. It is categorised as a Read tool in the Synaptex MCP Server, which means it retrieves data without modifying state.
Register the Synaptex MCP server in PolicyLayer and add a rule for synaptex_status: 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 Synaptex. Nothing to install.
synaptex_status 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 synaptex_status 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 synaptex_status. 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.
synaptex_status is provided by the Synaptex MCP server (jeromelabophy-gif/synaptex_claude). 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 →