AI agents call get_schema to retrieve information from Synapse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_schema is a read-only query that retrieves metadata about the graph structure. It queries and displays schema information without altering data, executing code, or triggering external operations. Lowest severity: schema introspection poses no immediate risk even if exposed to an AI agent, as it merely reveals the structure of the indexed codebase rather than enabling destructive or executing actions.
From the tool's definition Tool returns (retrieves) schema information: 'Return the full graph schema: node labels with properties, relationship types, and usage notes.' No modification, deletion, execution, or side effects described.
Attacks that exploit this kind of access
Return the full graph schema: node labels with properties, relationship types, and usage notes. It is categorised as a Read tool in the Synapse MCP Server, which means it retrieves data without modifying state.
Register the Synapse MCP server in PolicyLayer and add a rule for get_schema: 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 Synapse. Nothing to install.
get_schema 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_schema 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_schema. 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_schema is provided by the Synapse MCP server (synappscodecomprehension/synapps). 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 →