AI agents invoke csmar_query to trigger actions in CSMAR MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
While the description translates to 'general CSMAR data query' suggesting read-like behavior, a generic query tool against financial databases (financial statements, stock trading data) typically allows arbitrary SQL or structured queries to be executed.
From the tool's definition Tool name 'csmar_query' with description '通用 CSMAR 数据查询' (General CSMAR data query). The term 'query' combined with access to 240+ databases suggests arbitrary query execution capability.
Documented attack patterns abuse exactly the kind of access csmar_query 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:
{
"version": "1",
"default": "deny",
"tools": {
"csmar_query": {
"limits": [
{
"counter": "csmar_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}csmar_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
通用 CSMAR 数据查询. It is categorised as a Execute tool in the CSMAR MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CSMAR MCP Server MCP server in PolicyLayer and add a rule for csmar_query: 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 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the csmar_query 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. 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 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.