Check if a website supports AWAS (AI Web Action Standard). Returns a summary of the website
AI agents call awas_check_support to retrieve information from Qontinui MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a website to determine AWAS support status and returns a read-only summary. It performs no state changes, does not execute workflows or commands, and carries minimal risk if misused by an agent. The action is a passive check, not an operation that modifies, executes, or destroys resources.
From the tool's definition Tool description states it 'Check[s] if a website supports AWAS' and 'Returns a summary' — pure information retrieval with no modification, execution, or side effects.
Attacks that exploit this kind of access
Check if a website supports AWAS (AI Web Action Standard). Returns a summary of the website. It is categorised as a Read tool in the Qontinui MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for awas_check_support: 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_check_support is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the awas_check_support 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_check_support. 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_check_support 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 →