일정을 검색합니다 (제목, 설명에서 키워드 검색).
AI agents call search_calendar_events to retrieve information from OOSDK 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 based on search criteria (keywords in title and description). It has no side effects, does not modify or delete data, and does not trigger external operations. It is a straightforward data retrieval operation, fitting the 'Read' category. Severity is low because calendar event metadata is typically low-sensitivity information with limited blast radius if misused.
From the tool's definition Tool name 'search_calendar_events' and description indicate searching/querying calendar data by keyword in title and description fields. No modification, deletion, or execution capability is mentioned.
Attacks that exploit this kind of access
일정을 검색합니다 (제목, 설명에서 키워드 검색). It is categorised as a Read tool in the OOSDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for search_calendar_events: 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 OOSDK MCP Server. Nothing to install.
search_calendar_events 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 search_calendar_events 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 search_calendar_events. 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.
search_calendar_events is provided by the OOSDK MCP Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent_oosdk-public). 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 →