listings.invoke
Invoke a priced listing. Slice 1 returns a guided redirect to POST /v1/listings/:id/invoke — the marketplace flow with escrow, sealed input/output, and ed25519-signed completion is HTTP-only in this slice. Slice 2 will land sync-with-timeout MCP invocation.
This record as markdown: /tools/dev-agenttool-agenttool/listings.invoke.md
What listings.invoke does on Agenttool
AI agents invoke listings.invoke to trigger actions in Agenttool. 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 listings.invoke is rated High
listings.invoke 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
The rule that runs listings.invoke safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenttool, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listings.invoke, this is the rule to start with:
listings.invoke 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Agenttool, apply this rule, and every listings.invoke call is checked against it from then on.
Questions about listings.invoke
Invoke a priced listing. Slice 1 returns a guided redirect to POST /v1/listings/:id/invoke — the marketplace flow with escrow, sealed input/output, and ed25519-signed completion is HTTP-only in this slice. Slice 2 will land sync-with-timeout MCP invocation. It is categorised as a Execute tool in the Agenttool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agenttool MCP server in PolicyLayer and add a rule for listings.invoke: 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 Agenttool. Nothing to install.
listings.invoke is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the listings.invoke 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 listings.invoke. 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.
listings.invoke is provided by the Agenttool MCP server (https://api.agenttool.dev/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agenttool, and thousands of servers like it.
Across the catalogue