Return Synapse entity metadata by ID (projects, folders, files, tables, etc.). Only retrieves metadata information - does not download file content.
AI agents call get_entity 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 performs a straightforward data retrieval operation that queries Synapse metadata without modifying, executing, deleting, or financially affecting resources. The explicit statement that it does not download content and only retrieves metadata confirms it is a safe read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Return Synapse entity metadata by ID' and explicitly clarifies 'Only retrieves metadata information - does not download file content.' The verb 'Return' and 'retrieves' indicate a read-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_entity 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 get_entity:
{
"version": "1",
"default": "deny",
"tools": {
"get_entity": {}
}
}get_entity 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.
Return Synapse entity metadata by ID (projects, folders, files, tables, etc.). Only retrieves metadata information - does not download file content. 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 get_entity: 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.
get_entity 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 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. 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 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.