search_event
AI agents call search_event to retrieve information from Sola MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations on a stateless HTTP server serving Social Layer platform data are retrievals with no side effects. The tool searches or queries event data without modifying, deleting, or executing external operations. Confidence is slightly reduced due to missing description, but the naming convention and sibling tool patterns are clear indicators of a Read category operation.
From the tool's definition Tool name 'search_event' indicates a search operation on events; sibling tools include 'get_event', 'get_group', 'get_profile', 'get_venue', and 'list_event', all Read operations.
Attacks that exploit this kind of access
search_event. It is categorised as a Read tool in the Sola MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sola MCP Server MCP server in PolicyLayer and add a rule for search_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 Sola MCP Server. Nothing to install.
search_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 search_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 search_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.
search_event is provided by the Sola MCP Server MCP server (sociallayer-im/sola-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 →