AI agents call csmar_query_count to retrieve information from CSMAR 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 a count of records meeting specified criteria. It performs read-only data retrieval with no side effects—no creation, modification, deletion, or execution of commands. The aggregated count result has minimal blast radius even if misused by an agent, as it cannot alter state or trigger external operations.
From the tool's definition Tool name 'csmar_query_count' and description '查询满足条件的记录数量' (query the count of records matching conditions) indicates retrieval of aggregated data without modification.
Documented attack patterns abuse exactly the kind of access csmar_query_count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CSMAR MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for csmar_query_count:
{
"version": "1",
"default": "deny",
"tools": {
"csmar_query_count": {}
}
}csmar_query_count is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
查询满足条件的记录数量. It is categorised as a Read tool in the CSMAR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CSMAR MCP Server MCP server in PolicyLayer and add a rule for csmar_query_count: 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 CSMAR MCP Server. Nothing to install.
csmar_query_count 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 csmar_query_count 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 csmar_query_count. 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.
csmar_query_count is provided by the CSMAR MCP Server MCP server (ww11-max/csmar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CSMAR MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 CSMAR MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.