Locks the final slot (and optionally venue) and transitions a draft gathering to 'live'. Records the transition in the gathering events log. Does NOT send invites yet — call lyra_send_invite afterwards to start the RSVP flow. Calendar event creation on the host's connected calendar is a separate ...
Risk signalsHandles credentials or secrets (api_key)
Part of the Lyra Mcp Server server.
Free to start. No card required.
AI agents use lyra_finalise_gathering to initiate financial transactions through Lyra Mcp Server. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.
lyra_finalise_gathering moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.
Financial tools involve real money. Block by default and require explicit human approval before enabling.
{
"version": "1",
"default": "deny",
"tools": {
"lyra_finalise_gathering": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}See the full Lyra Mcp Server policy for all 34 tools.
These attack patterns abuse exactly the kind of access lyra_finalise_gathering gives an agent. Each links to the full case and the policy that stops it:
Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Locks the final slot (and optionally venue) and transitions a draft gathering to 'live'. Records the transition in the gathering events log. Does NOT send invites yet — call lyra_send_invite afterwards to start the RSVP flow. Calendar event creation on the host's connected calendar is a separate action in the Lyra web UI; this tool just locks the data. Requires API key authentication.. It is categorised as a Financial tool in the Lyra Mcp Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Lyra Mcp Server MCP server in PolicyLayer and add a rule for lyra_finalise_gathering: 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 Lyra Mcp Server. Nothing to install.
lyra_finalise_gathering 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 lyra_finalise_gathering 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 lyra_finalise_gathering. 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.
lyra_finalise_gathering is provided by the Lyra Mcp Server MCP server (https://mcp.checklyra.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 34 Lyra Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.