Returns a URL the user should open in their browser to connect a calendar. Google Calendar is supported today; Microsoft and Apple are planned. The user must be signed in to checklyra.com first. Once they grant consent, Lyra stores an encrypted refresh token and the connection becomes available t...
Risk signalsHandles credentials or secrets (api_key)
Part of the Lyra Mcp Server server.
Free to start. No card required.
AI agents use lyra_connect_calendar 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_connect_calendar 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_connect_calendar": {
"limits": [
{
"counter": "lyra_connect_calendar_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_connect_calendar 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.
Returns a URL the user should open in their browser to connect a calendar. Google Calendar is supported today; Microsoft and Apple are planned. The user must be signed in to checklyra.com first. Once they grant consent, Lyra stores an encrypted refresh token and the connection becomes available to other Convene tools. Requires API key authentication for the calling agent (so we know which user is asking).. 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_connect_calendar: 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_connect_calendar 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_connect_calendar 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_connect_calendar. 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_connect_calendar 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.