triggerDeploy · Pointsyeah MCP: Risk & Policy

WHAT IT DOES

What triggerDeploy does on Pointsyeah

AI agents invoke triggerDeploy to trigger actions in Pointsyeah. 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 triggerDeploy needs a policy

This tool executes a deployment action on a Rails application hosted on Hatchbox. Deployments are external operations whose effects (restarting services, updating production code, affecting live systems) depend on application state and deployment configuration. While not destructive per se, it triggers infrastructure changes that could impact availability and functionality, making it Execute rather than Write.

From the tool's definition Tool name 'triggerDeploy' and description 'Trigger a new deployment for your Rails application on Hatchbox. This tool initiates a deployment using Hatchbox' explicitly indicate execution of a deployment operation on external infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

triggerDeploy Rate-limited

triggerDeploy 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": {
    "triggerDeploy": {
      "limits": [
        {
          "counter": "triggerdeploy_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 Pointsyeah, so you can run agents against it safely.

FAQ

Questions about triggerDeploy

What does the triggerDeploy tool do? +

Trigger a new deployment for your Rails application on Hatchbox. This tool initiates a deployment using Hatchbox. It is categorised as a Execute tool in the Pointsyeah MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on triggerDeploy? +

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

What risk level is triggerDeploy? +

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

Can I rate-limit triggerDeploy? +

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

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

triggerDeploy is provided by the Pointsyeah MCP server (slack-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.