trigger_scan_run · Trackings MCP Server MCP: Risk & Policy

WHAT IT DOES

What trigger_scan_run does on Trackings MCP Server

AI agents invoke trigger_scan_run to trigger actions in Trackings 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_scan_run needs a policy

This tool triggers execution of a scan operation on an external service (trackings.ai). While not destructive or financial, it initiates an external operation whose effects depend on the scan configuration and external service behavior. The tool executes a defined workflow rather than merely reading or writing configuration data.

From the tool's definition Tool name 'trigger_scan_run' combined with description 'Trigger a scan run' indicates initiation of an external operation (scan execution). The server integrates with trackings.ai and performs 'trigger run executions' per the server description.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_scan_run Rate-limited

trigger_scan_run 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_scan_run": {
      "limits": [
        {
          "counter": "trigger_scan_run_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 Trackings MCP Server, so you can run agents against it safely.

FAQ

Questions about trigger_scan_run

What does the trigger_scan_run tool do? +

Trigger a scan run for an existing scan configuration. It is categorised as a Execute tool in the Trackings 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_scan_run? +

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

What risk level is trigger_scan_run? +

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

Can I rate-limit trigger_scan_run? +

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

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

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