mesh_compose

ONE-CALL: MCP Mesh composition / tool_policy pack for your server. Free 2/day then $0.20.

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

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What mesh_compose does on Dual Registry

AI agents call mesh_compose to retrieve information from Dual Registry without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`goals`	string	—
`listing_b`	string	—	Partner listing for used_with / execute_compose ladder
`agent_name`	string	—
`listing_id`	string	—
`tools_hint`	string	—
`payment_proof`	string	—

Parameters from the server's own tool schema.

RISK

Why mesh_compose is rated Low

Even though mesh_compose only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mesh_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 mesh_compose, this is the rule to start with:

mesh_compose Allowed

mesh_compose is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mesh_compose": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mesh_compose

What does the mesh_compose tool do? +

ONE-CALL: MCP Mesh composition / tool_policy pack for your server. Free 2/day then $0.20. It is categorised as a Read tool in the Dual Registry MCP Server, which means it retrieves data without modifying state.

What parameters does mesh_compose accept? +

mesh_compose accepts 6 parameters: goals, listing_b, agent_name, listing_id, tools_hint, payment_proof. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mesh_compose? +

Register the Dual Registry MCP server in PolicyLayer and add a rule for mesh_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 mesh_compose? +

mesh_compose is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mesh_compose? +

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

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

mesh_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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →