Execute an AWAS action on a website. The manifest must be discovered first using awas_discover. This tool makes the HTTP request defined by the action and returns the response.
AI agents invoke awas_execute to trigger actions in Qontinui MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This is an Execute-category tool because it runs external operations (HTTP requests to websites) triggered by user-supplied action manifests. The severity is high due to the potential blast radius: malicious or incorrectly-configured action manifests could alter website data, trigger unintended transactions, or perform unauthorized operations.
From the tool's definition Tool executes an action on a website by making an HTTP request with user-defined parameters. Description states 'Execute an AWAS action on a website' and 'makes the HTTP request defined by the action'.
Attacks that exploit this kind of access
Execute an AWAS action on a website. The manifest must be discovered first using awas_discover. This tool makes the HTTP request defined by the action and returns the response. It is categorised as a Execute tool in the Qontinui MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for awas_execute: 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 Qontinui MCP Server. Nothing to install.
awas_execute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the awas_execute 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 awas_execute. 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.
awas_execute is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-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 →