開催場所やキーワードでイベントを検索します。
AI agents call search_events_by_location to retrieve information from Connpass MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves event information based on search criteria (location and keyword). It performs data retrieval only, matching the 'Read' category definition. No data is created, modified, deleted, or financial transactions occur. Severity is low because unauthorized searches of public event data poses minimal risk.
From the tool's definition Tool name is 'search_events_by_location' and description states it searches events by location or keyword ('開催場所やキーワードでイベントを検索します' = 'search for events by location or keyword'). This is a query/search operation with no side effects.
Attacks that exploit this kind of access
開催場所やキーワードでイベントを検索します。. It is categorised as a Read tool in the Connpass MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Connpass MCP Server MCP server in PolicyLayer and add a rule for search_events_by_location: 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 Connpass MCP Server. Nothing to install.
search_events_by_location 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_events_by_location 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_events_by_location. 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_events_by_location is provided by the Connpass MCP Server MCP server (tyukei/commpass_mcp_server). 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 →