Low Risk

seo_score

Analyze markdown content for SEO quality and return a 0-100 score with grade. Basic scoring (heading structure, word count, keyword density, readability) requires no credentials and is FREE. Full analysis (issue list, prioritized suggestions, related-keyword gaps) costs 1 credit. Returns: { score...

Accepts raw HTML/template content (content)

Part of the Pipepost MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call seo_score to retrieve information from Pipepost without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though seo_score only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-mendlem-pipepost.yaml
tools:
  seo_score:
    rules:
      - action: allow

See the full Pipepost policy for all 29 tools.

Tool Name seo_score
Category Read
MCP Server Pipepost MCP Server
Risk Level Low

View all 29 tools →

Agents calling read-class tools like seo_score have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the seo_score tool do? +

Analyze markdown content for SEO quality and return a 0-100 score with grade. Basic scoring (heading structure, word count, keyword density, readability) requires no credentials and is FREE. Full analysis (issue list, prioritized suggestions, related-keyword gaps) costs 1 credit. Returns: { score, grade, breakdown, issues?, suggestions? }. Common errors: missing 'content' (VALIDATION_ERROR), insufficient credits for full analysis (PAYMENT_REQUIRED).. It is categorised as a Read tool in the Pipepost MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on seo_score? +

Add a rule in your Intercept YAML policy under the tools section for seo_score. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pipepost MCP server.

What risk level is seo_score? +

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

Can I rate-limit seo_score? +

Yes. Add a rate_limit block to the seo_score rule in your Intercept 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_score completely? +

Set action: deny in the Intercept policy for seo_score. 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_score? +

seo_score is provided by the Pipepost MCP server (pipepost-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Pipepost

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.