run_proactive_scan · surveyHelper MCP: Risk & Policy

WHAT IT DOES

What run_proactive_scan does on surveyHelper

AI agents invoke run_proactive_scan to trigger actions in surveyHelper. 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 run_proactive_scan needs a policy

This tool executes an external operation (querying arXiv for papers) rather than passively reading data. It initiates a background process with side effects (downloading/indexing papers), making it an Execute category risk. Severity is medium because the blast radius is limited to data retrieval and local storage—no financial impact, no destructive operations, and the external API call is read-only to arXiv.

From the tool's definition 'Kick off a background scan' indicates the tool triggers an external operation (arXiv API query) whose effects depend on configured interests and network state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_proactive_scan Rate-limited

run_proactive_scan 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": {
    "run_proactive_scan": {
      "limits": [
        {
          "counter": "run_proactive_scan_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 surveyHelper, so you can run agents against it safely.

FAQ

Questions about run_proactive_scan

What does the run_proactive_scan tool do? +

Kick off a background scan for new arXiv papers on your followed interests. It is categorised as a Execute tool in the surveyHelper MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_proactive_scan? +

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

What risk level is run_proactive_scan? +

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

Can I rate-limit run_proactive_scan? +

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

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

run_proactive_scan is provided by the surveyHelper MCP server (rich7420/surveyhelper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.