Search Synapse entities using keyword queries with optional name/type/parent filters.
AI agents call search_synapse to retrieve information from Synapse MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from Synapse without side effects. The search functionality returns matching entities based on keywords and filters but does not create, modify, delete, or execute any operations. It is a pure query operation consistent with Read category tools like get_entity and fetch operations.
From the tool's definition Tool description states 'Search Synapse entities using keyword queries' and 'get_entity_annotations, get_entity_children, get_entity_provenance' are sibling Read operations.
Documented attack patterns abuse exactly the kind of access search_synapse gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Synapse MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_synapse:
{
"version": "1",
"default": "deny",
"tools": {
"search_synapse": {}
}
}search_synapse is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Synapse entities using keyword queries with optional name/type/parent filters. It is categorised as a Read tool in the Synapse MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Synapse MCP Server MCP server in PolicyLayer and add a rule for search_synapse: 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 MCP Server. Nothing to install.
search_synapse 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 search_synapse 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 search_synapse. 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.
search_synapse is provided by the Synapse MCP Server MCP server (susheel/synapse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Synapse MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Synapse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.