Get the execution trace for a process instance — every activity that ran, in order. Activities with a \
AI agents call get_activity_history to retrieve information from CIB Seven MCP Server 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 execution history/audit trail information about a process instance. It retrieves data without modifying, executing, or deleting anything. The tool is read-only diagnostic access to process execution records, which is appropriate for investigation and diagnosis as stated in the server description.
From the tool's definition Tool name 'get_activity_history' and description 'Get the execution trace for a process instance — every activity that ran, in order' indicate retrieval of historical data with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get the execution trace for a process instance — every activity that ran, in order. Activities with a \. It is categorised as a Read tool in the CIB Seven MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CIB Seven MCP Server MCP server in PolicyLayer and add a rule for get_activity_history: 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 CIB Seven MCP Server. Nothing to install.
get_activity_history 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_activity_history 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_activity_history. 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_activity_history is provided by the CIB Seven MCP Server MCP server (krixerx/cib7-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 →