run_seo_audit

Run an SEO audit on the current page

Server Chromium ARM64 Browser nfodor/mcp-chromium-arm64
Category Read
Risk class Low
Parameters 00 required

What run_seo_audit does on Chromium ARM64 Browser

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

Why run_seo_audit needs a policy

An SEO audit inspects the current page's metadata, structure, and content to evaluate SEO factors. This is a read/analysis operation with no side effects. It does not modify data, execute arbitrary code, or perform destructive actions. Severity is low since it only reads the already-loaded page.

From the tool's definition 'Run an SEO audit on the current page' — reads and analyzes the current page's SEO properties without modifying anything

Questions about run_seo_audit

What does the run_seo_audit tool do? +

Run an SEO audit on the current page. It is categorised as a Read tool in the Chromium ARM64 Browser MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on run_seo_audit? +

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

What risk level is run_seo_audit? +

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

Can I rate-limit run_seo_audit? +

Yes. Add a rate_limit block to the run_seo_audit 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 run_seo_audit completely? +

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

run_seo_audit is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). 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.