AI agents call get_entity_schema_invalid_validations 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 validation results for inspection purposes only. It has no side effects, makes no modifications to data, and does not execute code or trigger external operations. The 'get_' prefix and passive 'Get...results' language confirm it is a read-only query operation. Blast radius is minimal—an agent can only retrieve metadata about validation failures, not affect data state.
From the tool's definition Tool name contains 'get_' and description states 'Get invalid validation results for a container' — this is a retrieval operation that queries validation data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get invalid validation results for a container. 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_entity_schema_invalid_validations: 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_entity_schema_invalid_validations 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_entity_schema_invalid_validations 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_entity_schema_invalid_validations. 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_entity_schema_invalid_validations 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 →