Returns rows from one or more Cargo tables on the targeted wiki, matching a SQL-style filter. Supports WHERE, JOIN ON, GROUP BY, HAVING, and ORDER BY clauses. Enabled only when the wiki has Cargo installed. Use cargo-list-tables to discover table names and cargo-describe-table to inspect field ty...
AI agents invoke cargo-query to trigger actions in MediaWiki 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.
Although the primary purpose is querying/reading data, the tool executes arbitrary SQL-style queries against the wiki's Cargo database, including JOIN, GROUP BY, and HAVING clauses. This constitutes executing dynamic queries rather than simple reads, and depending on the Cargo implementation could expose unintended data or be misused to probe database structure.
From the tool's definition Returns rows from one or more Cargo tables matching a SQL-style filter. Supports WHERE, JOIN ON, GROUP BY, HAVING, and ORDER BY clauses
Documented attack patterns abuse exactly the kind of access cargo-query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MediaWiki MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cargo-query:
{
"version": "1",
"default": "deny",
"tools": {
"cargo-query": {
"limits": [
{
"counter": "cargo-query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}cargo-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.
Returns rows from one or more Cargo tables on the targeted wiki, matching a SQL-style filter. Supports WHERE, JOIN ON, GROUP BY, HAVING, and ORDER BY clauses. Enabled only when the wiki has Cargo installed. Use cargo-list-tables to discover table names and cargo-describe-table to inspect field types before constructing a query — field types determine which operators apply (HOLDS / HOLDS LIKE for list fields, MATCHES for Searchtext, NEAR for Coordinates). Cargo collapses NULL to empty string on output, so. It is categorised as a Execute tool in the MediaWiki MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MediaWiki MCP Server MCP server in PolicyLayer and add a rule for cargo-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 MediaWiki MCP Server. Nothing to install.
cargo-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 cargo-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 cargo-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.
cargo-query is provided by the MediaWiki MCP Server MCP server (@professional-wiki/mediawiki-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MediaWiki 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.
38 MediaWiki MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.