AI agents call get_json_schema_body 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.
This tool retrieves and returns a JSON schema document without modifying, executing, or deleting any data. It is a read-only query operation consistent with other sibling tools on the server (get_entity_schema, get_entity_annotations, etc.). The blast radius is minimal—exposure of schema information presents low security risk in typical usage contexts.
From the tool's definition Tool name 'get_json_schema_body' with description 'Get the raw JSON schema document' indicates a retrieval operation with no mutation or side effects.
Attacks that exploit this kind of access
Get the raw JSON schema document. 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_json_schema_body: 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_json_schema_body 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_json_schema_body 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_json_schema_body. 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_json_schema_body is provided by the Synapse MCP server (sage-bionetworks/synapse-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 →