AI agents call aleph_get_entity_markdown to retrieve information from Barracuda without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns entity data by ID without creating, modifying, deleting, executing code, or moving funds. It has no side effects beyond returning information. Misuse would be limited to unauthorized information access, which is a low-severity read risk.
From the tool's definition Tool name 'aleph_get_entity_markdown' and description 'Fetch one entity by id and return full untruncated body text' indicate data retrieval with no modification or deletion. The verb 'Fetch' and action 'return' confirm read-only semantics.
Attacks that exploit this kind of access
Fetch one entity by id and return full untruncated body text. It is categorised as a Read tool in the Barracuda MCP Server, which means it retrieves data without modifying state.
Register the Barracuda MCP server in PolicyLayer and add a rule for aleph_get_entity_markdown: 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 Barracuda. Nothing to install.
aleph_get_entity_markdown 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 aleph_get_entity_markdown 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 aleph_get_entity_markdown. 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.
aleph_get_entity_markdown is provided by the Barracuda MCP server (sourcery-info/barracuda-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 →