AI agents use asset_replace to create or update resources in Voog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Voog environment.
This tool modifies assets reversibly by creating replacements. While it creates new assets (Write category), it does not permanently delete the original or execute arbitrary code. The incomplete description lowers confidence slightly, but the intent to create/replace assets clearly falls under Write rather than Destructive (since no explicit deletion is mentioned) or Read.
From the tool's definition Tool name 'asset_replace' and description 'Rename a layout_asset by creating a new one' indicates creation/modification of assets. The description is incomplete ('desired' is cut off), but the core operation is creating a new asset to replace an old one.
Attacks that exploit this kind of access
Rename a layout_asset by creating a new one with the desired. It is categorised as a Write tool in the Voog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Voog MCP server in PolicyLayer and add a rule for asset_replace: 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 Voog. Nothing to install.
asset_replace 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 asset_replace 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 asset_replace. 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.
asset_replace is provided by the Voog MCP server (runnel/voog-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 →