generate_profiling_script · Metis Public Health MCP

WHAT IT DOES

What generate_profiling_script does on Metis Public Health

AI agents invoke generate_profiling_script to trigger actions in Metis Public Health. 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 generate_profiling_script needs a policy

The name implies creating a script (likely for data profiling), which is an Execute-category action. The empty description lowers confidence, but 'script' generation in a data/research context typically produces executable code. Severity is high because a misused script-generation tool could produce and run harmful code. Confidence is moderate due to the empty description.

From the tool's definition Tool name contains 'generate' and 'script'; the sibling tool 'analyze_script' suggests scripts are generated and then executed or analyzed in this system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_profiling_script Rate-limited

generate_profiling_script 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": {
    "generate_profiling_script": {
      "limits": [
        {
          "counter": "generate_profiling_script_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 Metis Public Health, so you can run agents against it safely.

FAQ

Questions about generate_profiling_script

What does the generate_profiling_script tool do? +

generate_profiling_script. It is categorised as a Execute tool in the Metis Public Health MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_profiling_script? +

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

What risk level is generate_profiling_script? +

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

Can I rate-limit generate_profiling_script? +

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

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

generate_profiling_script is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.