Get statistics for filtering - available values for each filterable field
AI agents call get_filter_stats to retrieve information from MCP Product Management System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns statistical information about available filter values for product inventory fields. It has no side effects, does not execute commands, and does not create, modify, or delete data. It is a read-only operation that retrieves schema or metadata information to support filtering functionality.
From the tool's definition Tool name 'get_filter_stats' and description 'Get statistics for filtering - available values for each filterable field' indicate a retrieval operation that returns metadata about filterable fields without modifying any data.
Attacks that exploit this kind of access
Get statistics for filtering - available values for each filterable field. It is categorised as a Read tool in the MCP Product Management System MCP Server, which means it retrieves data without modifying state.
Register the MCP Product Management System MCP server in PolicyLayer and add a rule for get_filter_stats: 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 MCP Product Management System. Nothing to install.
get_filter_stats 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_filter_stats 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_filter_stats. 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_filter_stats is provided by the MCP Product Management System MCP server (pysorflow/mcpdemo). 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 →