Low Risk

query_model_statistics

[DEPRECATED] Get statistical summary of model contents. Use search_execute(query_type=

How to control query_model_statistics ↓

What query_model_statistics does on Engineering MCP Server

AI agents call query_model_statistics to retrieve information from Engineering MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why query_model_statistics needs a policy

This tool retrieves and summarizes existing model data. It does not create, modify, delete, or execute arbitrary operations. The incomplete description ('Use search_execute(query_type=') is truncated but does not suggest any capability beyond statistical analysis.

From the tool's definition Tool name 'query_model_statistics' and description 'Get statistical summary of model contents' indicate retrieval of aggregated data without modification.

Documented attack patterns abuse exactly the kind of access query_model_statistics gives an agent:

How to control query_model_statistics

PolicyLayer is an MCP gateway — it sits between your AI agents and Engineering MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_model_statistics:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_model_statistics": {}
  }
}

query_model_statistics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Engineering MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_model_statistics

What does the query_model_statistics tool do? +

[DEPRECATED] Get statistical summary of model contents. Use search_execute(query_type=. It is categorised as a Read tool in the Engineering MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_model_statistics? +

Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for query_model_statistics: 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 Engineering MCP Server. Nothing to install.

What risk level is query_model_statistics? +

query_model_statistics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_model_statistics? +

Yes. Add a rate_limit block to the query_model_statistics 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.

How do I block query_model_statistics completely? +

Set action: deny in the PolicyLayer policy for query_model_statistics. 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.

What MCP server provides query_model_statistics? +

query_model_statistics is provided by the Engineering MCP Server MCP server (puran-water/dexpi-sfiles-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Engineering MCP Server tool call.

Start from Engineering 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.

72 Engineering MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.