AI agents call get_process_insights to retrieve information from Blop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data analysis and reporting tool that extracts and transforms existing event data into process mining variants. It reads historical run health events and performs statistical or analytical operations to surface patterns. There is no capability to modify, delete, execute external operations, or move money. The optional PM4Py dependency is a passive analysis library, not an execution engine.
From the tool's definition Tool derives insights from existing run health events and processes them through process-mining analysis (PM4Py). The verb 'derive' and the passive framing 'from run health events' indicate read-only analysis with no side effects on the underlying data.
Attacks that exploit this kind of access
Derive process-mining style variants from run health events (optional PM4Py when installed). It is categorised as a Read tool in the Blop MCP Server, which means it retrieves data without modifying state.
Register the Blop MCP server in PolicyLayer and add a rule for get_process_insights: 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 Blop. Nothing to install.
get_process_insights 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_process_insights 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_process_insights. 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_process_insights is provided by the Blop MCP server (n2400813g/blop-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 →