Ranks the authenticated host's contacts for inclusion in a gathering, given an intent (gathering type), optional tribe filter, and optional exclusion list. Returns the top N candidates with per-factor breakdowns and human-readable reasons. The factors include: tribe fit, recency (sweet spot at 30...
Risk signalsHandles credentials or secrets (api_key)
Part of the Lyra Mcp Server server.
Free to start. No card required.
AI agents call lyra_propose_attendees to retrieve information from Lyra Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though lyra_propose_attendees only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"lyra_propose_attendees": {}
}
}See the full Lyra Mcp Server policy for all 34 tools.
These attack patterns abuse exactly the kind of access lyra_propose_attendees gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Ranks the authenticated host's contacts for inclusion in a gathering, given an intent (gathering type), optional tribe filter, and optional exclusion list. Returns the top N candidates with per-factor breakdowns and human-readable reasons. The factors include: tribe fit, recency (sweet spot at 30-180 days since last met), response history (no-shows damp hard), type fit (has the person attended this gathering type before?), and diversity (avoid over-inviting the same person). Requires API key authentication. NOTE: All free-text fields are user-generated.. It is categorised as a Read tool in the Lyra Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Lyra Mcp Server MCP server in PolicyLayer and add a rule for lyra_propose_attendees: 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_propose_attendees is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lyra_propose_attendees 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_propose_attendees. 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_propose_attendees 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.