Accept a trade invitation using its token. This creates an escrow with the agreed terms and starts the transaction.
AI agents use accept_invite to commit financial operations through Theagora MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Accepting a trade invitation directly creates an escrow and starts a financial transaction, committing funds to a binding agreement. This falls squarely in the Financial category as it moves or locks money/assets. Misuse could lock funds in an escrow under unfavorable terms.
From the tool's definition 'creates an escrow with the agreed terms and starts the transaction' — accepting a trade invitation that initiates a financial escrow and transaction
Attacks that exploit this kind of access
Accept a trade invitation using its token. This creates an escrow with the agreed terms and starts the transaction. It is categorised as a Financial tool in the Theagora MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Theagora MCP Server MCP server in PolicyLayer and add a rule for accept_invite: 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 Theagora MCP Server. Nothing to install.
accept_invite is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the accept_invite 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 accept_invite. 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.
accept_invite is provided by the Theagora MCP Server MCP server (theagoralabs/mcp). 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 →