AI agents call get_project_history to retrieve information from Vaiz MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical activity logs for a project—a read-only operation with no side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because accessing historical project data poses minimal risk; it does not execute code, modify data, delete records, or commit financial obligations.
From the tool's definition Tool name 'get_project_history' and description 'Get history of all activities in a specific project' indicate retrieval of historical data with no modification, creation, or deletion.
Attacks that exploit this kind of access
Get history of all activities in a specific project across the workspace. It is categorised as a Read tool in the Vaiz MCP MCP Server, which means it retrieves data without modifying state.
Register the Vaiz MCP server in PolicyLayer and add a rule for get_project_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 Vaiz MCP. Nothing to install.
get_project_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_project_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_project_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_project_history is provided by the Vaiz MCP server (vaizcom/vaiz-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 →