Replace a specific link URL in a post/page. Finds the old URL and replaces it with a new one.
AI agents use update_link to create or update resources in Noleemits Vision Builder MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Noleemits Vision Builder MCP environment.
This tool modifies content (updates URLs in posts/pages) but the change is reversible—the old URL can be replaced again if needed. It does not delete data, execute arbitrary code, move money, or create irreversible changes.
From the tool's definition Tool description states 'Replace a specific link URL in a post/page. Finds the old URL and replaces it with a new one.' This is a reversible modification operation that updates existing content.
Attacks that exploit this kind of access
Replace a specific link URL in a post/page. Finds the old URL and replaces it with a new one. It is categorised as a Write tool in the Noleemits Vision Builder MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for update_link: 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 Noleemits Vision Builder MCP. Nothing to install.
update_link 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 update_link 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 update_link. 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.
update_link is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-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 →