trigger_report · SurfRank MCP Server MCP: Risk & Policy

WHAT IT DOES

What trigger_report does on SurfRank MCP Server

AI agents invoke trigger_report to trigger actions in SurfRank MCP Server. 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.

WHY IT NEEDS A POLICY

Why trigger_report needs a policy

trigger_report queues an external report generation process rather than passively retrieving data. It consumes credits based on parameters (keywords and engines selected), making it an Execute-category tool that runs an operation whose effects depend on the arguments provided.

From the tool's definition Tool description states 'Queue a new AI-visibility report' which triggers an external operation (report generation) that incurs costs (0.3 credits × keywords × engines). This is an action that initiates a process with resource consumption and side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_report Rate-limited

trigger_report 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": {
    "trigger_report": {
      "limits": [
        {
          "counter": "trigger_report_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SurfRank MCP Server, so you can run agents against it safely.

FAQ

Questions about trigger_report

What does the trigger_report tool do? +

Queue a new AI-visibility report for a project. Cost: 0.3 credits × keywords × engines. It is categorised as a Execute tool in the SurfRank MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_report? +

Register the SurfRank MCP Server MCP server in PolicyLayer and add a rule for trigger_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 SurfRank MCP Server. Nothing to install.

What risk level is trigger_report? +

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

Can I rate-limit trigger_report? +

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

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

trigger_report is provided by the SurfRank MCP Server MCP server (surfrankai/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.