Publish an API contract, interface definition, or schema that other agents can reference.
AI agents use publish_spec to create or update resources in Interagent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Interagent environment.
This tool creates or modifies shared specifications that other agents depend on. While reversible (specs can typically be updated or deprecated), publishing a spec can affect downstream agents' behavior and coordination. It does not retrieve data (Read), execute arbitrary code (Execute), delete irreversibly (Destructive), or move money (Financial).
From the tool's definition The tool description states it will 'Publish an API contract, interface definition, or schema' — publishing is a create/modify operation that adds or updates shared reference data for other agents.
Attacks that exploit this kind of access
Publish an API contract, interface definition, or schema that other agents can reference. It is categorised as a Write tool in the Interagent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Interagent MCP server in PolicyLayer and add a rule for publish_spec: 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 Interagent. Nothing to install.
publish_spec is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the publish_spec 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.
Set action: deny in the PolicyLayer policy for publish_spec. 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.
publish_spec is provided by the Interagent MCP server (signalclaude/interagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →