Run an 18-check data quality scan over the tenant
AI agents call qbo_analyze_data_quality to retrieve information from Kaizen Qbo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A data quality scan is a non-destructive analytical operation that inspects existing data and returns findings. It does not create, modify, delete, or execute financial transactions. The 'scan' language further reinforces that this is a passive read-only inspection tool. While it operates on financial data, it does not move money or commit financial obligations.
From the tool's definition Tool name 'qbo_analyze_data_quality' and description 'Run an 18-check data quality scan over the tenant' indicate a diagnostic/auditing operation that queries and reports on data state without modifying, deleting, or executing transactions.
Attacks that exploit this kind of access
Run an 18-check data quality scan over the tenant. It is categorised as a Read tool in the Kaizen Qbo MCP Server, which means it retrieves data without modifying state.
Register the Kaizen Qbo MCP server in PolicyLayer and add a rule for qbo_analyze_data_quality: 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 Kaizen Qbo. Nothing to install.
qbo_analyze_data_quality 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 qbo_analyze_data_quality 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 qbo_analyze_data_quality. 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.
qbo_analyze_data_quality is provided by the Kaizen Qbo MCP server (kaizen-qbo-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 →