Gets detailed information about a specific calendar event
AI agents call get-event to retrieve information from Outlook MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar event information without creating, modifying, deleting, or executing any actions. It is a straightforward read operation with minimal security risk, as it only queries existing data. Severity is low because calendar event details typically contain scheduling information with limited sensitive data exposure compared to email content or financial transactions.
From the tool's definition Tool name 'get-event' and description 'Gets detailed information about a specific calendar event' indicate pure data retrieval with no modifications, side effects, or external operations triggered.
Attacks that exploit this kind of access
Gets detailed information about a specific calendar event. It is categorised as a Read tool in the Outlook MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Outlook MCP Server MCP server in PolicyLayer and add a rule for get-event: 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 Outlook MCP Server. Nothing to install.
get-event 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 get-event 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 get-event. 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.
get-event is provided by the Outlook MCP Server MCP server (peacockery-studio/outlook-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 →