Browse statistics tables in a category
AI agents call browse_statistics to retrieve information from Stefanoamorelli Rik without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays statistics from the Estonian Business Register, which is a data query operation with no side effects. It does not create, modify, delete, or execute external operations. The sibling tools (check_data_availability, get_annual_reports, get_company_details, etc.) all indicate a Read-focused MCP server for querying business registry information.
From the tool's definition Tool name 'browse_statistics' and description 'Browse statistics tables in a category' indicate a read-only operation that retrieves or queries statistical data without modification or deletion. The verb 'browse' denotes passive data access.
Attacks that exploit this kind of access
Browse statistics tables in a category. It is categorised as a Read tool in the Stefanoamorelli Rik MCP Server, which means it retrieves data without modifying state.
Register the Stefanoamorelli Rik MCP server in PolicyLayer and add a rule for browse_statistics: 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 Stefanoamorelli Rik. Nothing to install.
browse_statistics 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 browse_statistics 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 browse_statistics. 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.
browse_statistics is provided by the Stefanoamorelli Rik MCP server (@iflow-mcp/stefanoamorelli-rik-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 →