AI agents call query_page to retrieve information from Tauri Plugin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries state information from the current page (DOM, content, etc.) without creating, modifying, deleting, or executing anything. It is a read-only diagnostic operation with no side effects. Even though it operates on a Tauri application under debug control, the action itself is passive data retrieval, making it a Read risk category.
From the tool's definition The tool 'query_page' is described as inspecting the current page, with 'Modes' listed but not detailed. The verb 'inspect' and the name 'query_page' both indicate information retrieval without modification.
Documented attack patterns abuse exactly the kind of access query_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tauri Plugin, and nothing reaches the server without passing your rules. This is the rule we recommend for query_page:
{
"version": "1",
"default": "deny",
"tools": {
"query_page": {}
}
}query_page 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.
Inspects the current page. Modes:. It is categorised as a Read tool in the Tauri Plugin MCP Server, which means it retrieves data without modifying state.
Register the Tauri Plugin MCP server in PolicyLayer and add a rule for query_page: 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 Tauri Plugin. Nothing to install.
query_page 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 query_page 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 query_page. 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.
query_page is provided by the Tauri Plugin MCP server (p3gleg/tauri-plugin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Tauri Plugin tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Tauri Plugin tools catalogued and risk-classified — across an index of 42,500+ MCP servers.