check_synapse_id

Validate whether a Synapse ID exists.

Server Synapse sage-bionetworks/synapse-mcp
Category Read
Risk class Low
Parameters 00 required

What check_synapse_id does on Synapse

AI agents call check_synapse_id 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.

Why check_synapse_id needs a policy

This tool performs a simple validation/existence check, which is a read-only operation with no side effects. It retrieves information (whether an ID is valid) without creating, modifying, or destroying any data. The blast radius of misuse is minimal—an agent could spam validation requests but cannot access sensitive data, modify resources, or trigger external operations.

From the tool's definition Tool name 'check_synapse_id' and description 'Validate whether a Synapse ID exists' indicates a query operation that checks existence without modifying, creating, or deleting data.

Questions about check_synapse_id

What does the check_synapse_id tool do? +

Validate whether a Synapse ID exists. It is categorised as a Read tool in the Synapse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_synapse_id? +

Register the Synapse MCP server in PolicyLayer and add a rule for check_synapse_id: 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.

What risk level is check_synapse_id? +

check_synapse_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_synapse_id? +

Yes. Add a rate_limit block to the check_synapse_id 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.

How do I block check_synapse_id completely? +

Set action: deny in the PolicyLayer policy for check_synapse_id. 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.

What MCP server provides check_synapse_id? +

check_synapse_id 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.