✏️ UPDATE WEBHOOK - Modify existing webhook configuration including endpoint URL and event type. Use this for changing integration endpoints, updating event subscriptions, fixing broken webhook URLs, and adapting to system changes. Essential for maintaining active integrations and ensuring contin...
AI agents use tiendanube_update_webhook to create or update resources in Tienda Nube MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tienda Nube MCP Server environment.
Updating a webhook modifies system configuration reversibly. While it affects critical integration infrastructure and could be misused to redirect sensitive data to an attacker-controlled endpoint, it is not irreversible (webhooks can be reconfigured again) and does not directly execute code or trigger financial transactions.
From the tool's definition Tool name includes 'update', description explicitly states 'Modify existing webhook configuration including endpoint URL and event type'. Webhooks are configuration entities that control data flow and system integration.
Attacks that exploit this kind of access
✏️ UPDATE WEBHOOK - Modify existing webhook configuration including endpoint URL and event type. Use this for changing integration endpoints, updating event subscriptions, fixing broken webhook URLs, and adapting to system changes. Essential for maintaining active integrations and ensuring continuous data flow between systems. It is categorised as a Write tool in the Tienda Nube MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tienda Nube MCP Server MCP server in PolicyLayer and add a rule for tiendanube_update_webhook: 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 Tienda Nube MCP Server. Nothing to install.
tiendanube_update_webhook 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 tiendanube_update_webhook 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 tiendanube_update_webhook. 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.
tiendanube_update_webhook is provided by the Tienda Nube MCP Server MCP server (pedrohsguimaraes/nuvem-shop-mcp-server). 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 →