run_analysis · Wellness Planner MCP: Risk & Policy

WHAT IT DOES

What run_analysis does on Wellness Planner

AI agents invoke run_analysis to trigger actions in Wellness Planner. 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_analysis needs a policy

The tool appears to execute analysis operations against health and task data. While the empty description limits confidence, the name and server context suggest it runs code or algorithms whose effects depend on inputs (which data to analyze, what parameters to use). This qualifies as Execute rather than Read (which would be passive retrieval) or Write (which would explicitly state data modification).

From the tool's definition Tool name 'run_analysis' combined with server context involving 'calculated readiness scores', 'optimized daily schedules', and 'local SQLite database' suggests execution of analysis algorithms or queries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_analysis Rate-limited

run_analysis 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_analysis": {
      "limits": [
        {
          "counter": "run_analysis_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 Wellness Planner, so you can run agents against it safely.

FAQ

Questions about run_analysis

What does the run_analysis tool do? +

run_analysis. It is categorised as a Execute tool in the Wellness Planner 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_analysis? +

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

What risk level is run_analysis? +

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

Can I rate-limit run_analysis? +

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

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

run_analysis is provided by the Wellness Planner MCP server (rwking/wellness_planner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.