Create or reactivate a link between an AnchorID and a source record.
AI agents use link_source_record to create or update resources in Anchord MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anchord MCP environment.
This tool creates or reactivates associations in the identity resolution system. While it modifies state, the operation is reversible (links can be removed or updated later). The context of Anchord as an identity resolution platform suggests this affects data relationships rather than destroying them.
From the tool's definition Tool description states 'Create or reactivate a link' which are reversible write operations. The tool modifies the relationship between an AnchorID and source records without permanently deleting data.
Attacks that exploit this kind of access
Create or reactivate a link between an AnchorID and a source record. It is categorised as a Write tool in the Anchord MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anchord MCP server in PolicyLayer and add a rule for link_source_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 Anchord MCP. Nothing to install.
link_source_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the link_source_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 link_source_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.
link_source_record is provided by the Anchord MCP server (nolenation04/anchord-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 →