get_entity_annotations

THE RISK

Low Risk

Why get_entity_annotations needs a policy

This tool retrieves metadata (annotations) associated with a Synapse entity. It has no side effects, does not modify or delete data, and does not trigger external operations. It is a straightforward data query operation consistent with the Read category.

From the tool's definition Tool name is 'get_entity_annotations' and description states 'Return custom annotation key/value pairs' — both indicate a retrieval operation with no modification or deletion.

Documented attack patterns abuse exactly the kind of access get_entity_annotations gives an agent:

POLICY

How to control get_entity_annotations

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_annotations:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_entity_annotations": {}
  }
}

get_entity_annotations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Synapse MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Synapse MCP Server tools

Read get_entity Return Synapse entity metadata by ID (projects, folders, files, tables, etc.). Only retrie Read get_entity_children List children for Synapse container entities (projects or folders). Read get_entity_provenance Return provenance (activity) metadata for a Synapse entity, including inputs and code exec Read search_synapse Search Synapse entities using keyword queries with optional name/type/parent filters.

All 5 Synapse MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_entity_annotations

What does the get_entity_annotations tool do? +

Return custom annotation key/value pairs for a Synapse entity. It is categorised as a Read tool in the Synapse MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_entity_annotations? +

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

What risk level is get_entity_annotations? +

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

Can I rate-limit get_entity_annotations? +

Yes. Add a rate_limit block to the get_entity_annotations 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 get_entity_annotations completely? +

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

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

Enforce policy on every Synapse MCP Server tool call.

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.

CHECK YOUR STACK →