AI agents invoke smw-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.
The tool 'runs' a Semantic MediaWiki query, which is an execution of a query engine. While likely read-only in practice (SMW queries retrieve semantic data), the description is truncated and incomplete, so we cannot confirm it has no side effects. 'Runs' implies execution rather than a simple retrieval. Confidence is reduced due to the incomplete description.
From the tool's definition Tool name 'smw-query' and partial description 'Runs a Semantic MediaWiki' indicate execution of a query against Semantic MediaWiki
Documented attack patterns abuse exactly the kind of access smw-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 smw-query:
{
"version": "1",
"default": "deny",
"tools": {
"smw-query": {
"limits": [
{
"counter": "smw-query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} smw-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.
Runs a Semantic MediaWiki. 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 smw-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.
smw-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 smw-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 smw-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.
smw-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.