seo_audit_performance

Audit HTML structure and content for SEO performance factors

SERVERPlugin Hub SOURCE@barnburner121/plugin-hub-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/barnburner121-plugin-hub-mcp/seo-audit-performance.md

WHAT IT DOES

What seo_audit_performance does on Plugin Hub

AI agents invoke seo_audit_performance to trigger actions in Plugin Hub. 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.

RISK

Why seo_audit_performance is rated High

seo_audit_performance triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seo_audit_performance safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Plugin Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seo_audit_performance, this is the rule to start with:

seo_audit_performance Rate-limited

seo_audit_performance stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "seo_audit_performance": {
      "limits": [
        {
          "counter": "seo_audit_performance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Plugin Hub, apply this rule, and every seo_audit_performance call is checked against it from then on.

FAQ

Questions about seo_audit_performance

What does the seo_audit_performance tool do? +

Audit HTML structure and content for SEO performance factors. It is categorised as a Execute tool in the Plugin Hub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on seo_audit_performance? +

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

What risk level is seo_audit_performance? +

seo_audit_performance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit seo_audit_performance? +

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

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

seo_audit_performance is provided by the Plugin Hub MCP server (@barnburner121/plugin-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Plugin Hub, and thousands of servers like it.

This server

All 616 Plugin Hub tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →