seo_cannibalization_report

A write tool on the Postking MCP server.

SERVERPostking Mcp SOURCEpostking-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/seo-cannibalization-report.md

WHAT IT DOES

What seo_cannibalization_report does on Postking Mcp

AI agents use seo_cannibalization_report to create or update resources in Postking Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Postking Mcp environment.

RISK

Why seo_cannibalization_report is rated Medium

An AI agent can call seo_cannibalization_report faster than any human can review: one bad instruction and it creates or modifies resources in Postking Mcp by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seo_cannibalization_report safely

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

seo_cannibalization_report Rate-limited

seo_cannibalization_report stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_cannibalization_report": {
      "limits": [
        {
          "counter": "seo_cannibalization_report_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about seo_cannibalization_report

What does the seo_cannibalization_report tool do? +

seo_cannibalization_report is a write tool on the Postking MCP server. It is categorised as a Write tool in the Postking Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on seo_cannibalization_report? +

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

What risk level is seo_cannibalization_report? +

seo_cannibalization_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit seo_cannibalization_report? +

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

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

seo_cannibalization_report is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What seo_cannibalization_report does on Postking Mcp

Why seo_cannibalization_report is rated Medium

The rule that runs seo_cannibalization_report safely

Questions about seo_cannibalization_report

More on Postking, and thousands of servers like it.