Queues an invite to one of the gathering's invitees. Generates a secure RSVP token, stamps invited_at, persists a gathering_invite_messages row with delivery_status='queued', and appends gathering_invite_sent to the audit log. Returns the rsvp_url for the invitee. ACTUAL EMAIL SEND IS NOT TRIGGER...
Risk signalsHandles credentials or secrets (api_key)
Part of the Lyra Mcp Server server.
Free to start. No card required.
AI agents use lyra_send_invite to create or modify resources in Lyra Mcp Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call lyra_send_invite repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Lyra Mcp Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"lyra_send_invite": {
"limits": [
{
"counter": "lyra_send_invite_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Lyra Mcp Server policy for all 34 tools.
These attack patterns abuse exactly the kind of access lyra_send_invite gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Queues an invite to one of the gathering's invitees. Generates a secure RSVP token, stamps invited_at, persists a gathering_invite_messages row with delivery_status='queued', and appends gathering_invite_sent to the audit log. Returns the rsvp_url for the invitee. ACTUAL EMAIL SEND IS NOT TRIGGERED BY THIS TOOL — it queues the data and a lyra-side worker (or manual flow) sends via Resend with allowlist gating. This keeps the MCP server free of Resend credentials and gives a single chokepoint for anti-spam. Requires API key authentication. NOTE: All fields are user-generated.. It is categorised as a Write tool in the Lyra Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lyra Mcp Server MCP server in PolicyLayer and add a rule for lyra_send_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 Lyra Mcp Server. Nothing to install.
lyra_send_invite 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 lyra_send_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 lyra_send_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.
lyra_send_invite 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.