AI agents use media_set_update_asset_titles 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 asset metadata (titles) within a media set, which is a reversible write operation. It has medium severity because misconfiguration could affect multiple assets simultaneously ('one or more'), potentially impacting site appearance or organization, but the operation is non-destructive and can be undone. Confidence is high due to clear language in both the name and description.
From the tool's definition Tool name 'media_set_update_asset_titles' contains 'update'; description states 'edit one or more asset titles'—these are explicit write operations that modify existing data.
Attacks that exploit this kind of access
Safely edit one or more asset titles in a media_set. 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 media_set_update_asset_titles: 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.
media_set_update_asset_titles 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 media_set_update_asset_titles 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 media_set_update_asset_titles. 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.
media_set_update_asset_titles 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 →