fetch the full record behind any at-uri (e.g. a string/paste, comment,
AI agents call get_record to retrieve information from Tangled 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 data from an AT Protocol URI and returns the full record. It performs a query operation with no side effects, no data modification, no code execution, and no destructive actions. The operation is read-only and safe for retrieval of existing records (strings, pastes, comments, etc.).
From the tool's definition Tool name 'get_record' with description 'fetch the full record behind any at-uri' — the verb 'fetch' indicates data retrieval without modification.
Attacks that exploit this kind of access
fetch the full record behind any at-uri (e.g. a string/paste, comment,. It is categorised as a Read tool in the Tangled MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tangled MCP Server MCP server in PolicyLayer and add a rule for get_record: 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 Tangled MCP Server. Nothing to install.
get_record 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_record 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_record. 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_record is provided by the Tangled MCP Server MCP server (zzstoatzz/tangled-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_record is one line of Tangled MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →