runAutoActions · Knowledge MCP Server MCP: Risk & Policy

WHAT IT DOES

What runAutoActions does on Knowledge MCP Server

AI agents invoke runAutoActions to trigger actions in Knowledge 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 runAutoActions needs a policy

This tool triggers multiple automated operations (reschedule, split, prioritize, cleanup, inject) in a single atomic commit to a GitHub repository. It executes a chain of actions that modify the knowledge base, making it an Execute-category tool.

From the tool's definition 'Run all auto-optimizations: reschedule, split, prioritize, cleanup, inject' and 'then false to apply. One atomic commit.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

runAutoActions Rate-limited

runAutoActions 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": {
    "runAutoActions": {
      "limits": [
        {
          "counter": "runautoactions_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 Knowledge MCP Server, so you can run agents against it safely.

FAQ

Questions about runAutoActions

What does the runAutoActions tool do? +

Run all auto-optimizations: reschedule, split, prioritize, cleanup, inject. Always dryRun=true first to preview, then false to apply. One atomic commit. It is categorised as a Execute tool in the Knowledge 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 runAutoActions? +

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

What risk level is runAutoActions? +

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

Can I rate-limit runAutoActions? +

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

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

runAutoActions is provided by the Knowledge MCP Server MCP server (vuluu2k/knowledge_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.