get_basic_stats
AI agents call get_basic_stats to retrieve information from Process Mining MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_basic_stats' tool appears to retrieve statistical information from process mining event log data stored in PostgreSQL. This is a read-only retrieval operation with no side effects. The sibling tools provide strong contextual evidence that this is part of an analysis/query suite rather than a data modification or execution tool.
From the tool's definition Tool name 'get_basic_stats' and server context indicate data retrieval. The tool is listed among sibling tools like 'analyze_activities', 'analyze_performance', 'analyze_variants', and 'search_tickets' which are all read/query operations on process mining…
Attacks that exploit this kind of access
get_basic_stats. It is categorised as a Read tool in the Process Mining MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Process Mining MCP Server MCP server in PolicyLayer and add a rule for get_basic_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 Process Mining MCP Server. Nothing to install.
get_basic_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_basic_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_basic_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_basic_stats is provided by the Process Mining MCP Server MCP server (mostapow/mcp4pm). 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 →