deploy_marketplace_template · PlugLayer MCP Server MCP

WHAT IT DOES

What deploy_marketplace_template does on PlugLayer MCP Server

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

This tool performs infrastructure deployment—a non-reversible operational effect that depends on template selection and project context arguments. While deployment itself may be partially undoable via delete_deployment, the immediate action is to execute a deployment workflow, not to reverse one.

From the tool's definition Tool description explicitly states it 'deploy[s] a marketplace template into an existing project', which constitutes triggering external infrastructure operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_marketplace_template Rate-limited

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

FAQ

Questions about deploy_marketplace_template

What does the deploy_marketplace_template tool do? +

Deploy a marketplace template into an existing project or a brand-new project created during the same flow. Secret-like required env vars are auto-resolved here before the deploy request is sent. It is categorised as a Execute tool in the PlugLayer 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 deploy_marketplace_template? +

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

What risk level is deploy_marketplace_template? +

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

Can I rate-limit deploy_marketplace_template? +

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

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

deploy_marketplace_template is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.