execute_compose

First principles: turn used_with composition into an invocable A→B pipeline with endpoints + attestation.

SERVERDual Registry SOURCEhttps://www.dualregistry.dev/api/protocol

High RISK CLASS

Category Execute

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-dualregistry-registry/execute-compose.md

WHAT IT DOES

What execute_compose does on Dual Registry

AI agents invoke execute_compose to trigger actions in Dual Registry. 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.

Parameter	Type	Required
`from`	string	—
`listing_b`	string	Yes
`listing_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why execute_compose is rated High

execute_compose triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs execute_compose safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dual Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_compose, this is the rule to start with:

execute_compose Rate-limited

execute_compose 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": {
    "execute_compose": {
      "limits": [
        {
          "counter": "execute_compose_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dual Registry, apply this rule, and every execute_compose call is checked against it from then on.

FAQ

Questions about execute_compose

What does the execute_compose tool do? +

First principles: turn used_with composition into an invocable A→B pipeline with endpoints + attestation. It is categorised as a Execute tool in the Dual Registry MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does execute_compose accept? +

execute_compose accepts 3 parameters: from, listing_b, listing_id. Required: listing_b, listing_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on execute_compose? +

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

What risk level is execute_compose? +

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

Can I rate-limit execute_compose? +

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

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

execute_compose is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dual Registry, and thousands of servers like it.

This server

All 64 Dual Registry tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →