audit_tokens

Audit a live URL

Server OverlayQA MCP overlayqa/mcp
Category Read
Risk class Low
Parameters 00 required

What audit_tokens does on OverlayQA MCP

AI agents call audit_tokens to retrieve information from OverlayQA MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why audit_tokens needs a policy

This tool retrieves and analyzes data from a web page (WCAG accessibility and color-contrast metrics). It does not create, modify, delete, or execute code—it only inspects and reports. No side effects or irreversible changes occur. Severity is low because even if misused, an audit produces only informational output with no blast radius.

From the tool's definition Tool name is 'audit_tokens' and description states 'Audit a live URL' — auditing is a read-only inspection activity.

Questions about audit_tokens

What does the audit_tokens tool do? +

Audit a live URL. It is categorised as a Read tool in the OverlayQA MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on audit_tokens? +

Register the OverlayQA MCP server in PolicyLayer and add a rule for audit_tokens: 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 OverlayQA MCP. Nothing to install.

What risk level is audit_tokens? +

audit_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit audit_tokens? +

Yes. Add a rate_limit block to the audit_tokens 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.

How do I block audit_tokens completely? +

Set action: deny in the PolicyLayer policy for audit_tokens. 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.

What MCP server provides audit_tokens? +

audit_tokens is provided by the OverlayQA MCP server (overlayqa/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.