AI agents call count_records to retrieve information from Qtz Iris without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
where | string | — | WHERE 子句（可选） |
tableName | string | Yes | 表名或类名 |
Parameters from the server's own tool schema.
This tool performs a read-only statistical query on table records. It retrieves a count metric without side effects, making it a Read operation with low severity—misuse would only expose data cardinality, not enable destructive or financial actions.
From the tool's definition Tool name 'count_records' and description '统计表中的记录数' (count records in a table) indicates a query operation that retrieves aggregate data without modifying or deleting anything.
Attacks that exploit this kind of access
统计表中的记录数. It is categorised as a Read tool in the Qtz Iris MCP Server, which means it retrieves data without modifying state.
count_records accepts 2 parameters: where, tableName. Required: tableName. The full parameter table on this page comes from the server's own tool schema.
Register the Qtz Iris MCP server in PolicyLayer and add a rule for count_records: 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 Qtz Iris. Nothing to install.
count_records 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 count_records 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 count_records. 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.
count_records is provided by the Qtz Iris MCP server (qtz-iris-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 →