new_heim_application · Heim MCP: Risk & Policy

WHAT IT DOES

What new_heim_application does on Heim MCP

AI agents invoke new_heim_application to trigger actions in Heim MCP. 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 new_heim_application needs a policy

Creating a new application is an Execute action—it triggers external operations (application scaffolding, initialization, provisioning) whose effects depend on arguments (application name, configuration). While not immediately destructive, misuse could consume cloud resources, create orphaned applications, or establish unintended infrastructure.

From the tool's definition Tool name 'new_heim_application' and server description indicate it creates backend applications. Sibling tools include 'deploy_heim_application' and 'heim_start', confirming this tool triggers application creation/initialization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

new_heim_application Rate-limited

new_heim_application 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": {
    "new_heim_application": {
      "limits": [
        {
          "counter": "new_heim_application_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 Heim MCP, so you can run agents against it safely.

FAQ

Questions about new_heim_application

What does the new_heim_application tool do? +

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

How do I enforce a policy on new_heim_application? +

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

What risk level is new_heim_application? +

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

Can I rate-limit new_heim_application? +

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

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

new_heim_application is provided by the Heim MCP server (nor2-io/heim-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.