list_filters
AI agents call list_filters to retrieve information from Microsoft Events MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name 'list_filters' combined with its placement on a server dedicated to searching and analyzing Microsoft events indicates this returns metadata about available filters rather than modifying or executing operations. This is a read-only data retrieval action.
From the tool's definition Tool named 'list_filters' with empty description on an Events MCP Server alongside 'search_events', 'get_event_details', and 'get_event_stats'. The naming and context strongly suggest it retrieves available filter options for querying events.
Attacks that exploit this kind of access
list_filters. It is categorised as a Read tool in the Microsoft Events MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Events MCP Server MCP server in PolicyLayer and add a rule for list_filters: 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 Microsoft Events MCP Server. Nothing to install.
list_filters 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 list_filters 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 list_filters. 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.
list_filters is provided by the Microsoft Events MCP Server MCP server (trsdn/msevent-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 →