fleet_get_query_results

THE RISK

Low Risk

Why fleet_get_query_results needs a policy

The tool fetches or retrieves existing query results without modifying, deleting, or executing new operations. This is consistent with Read category semantics. Low severity reflects limited blast radius—an agent retrieving query results poses minimal risk unless the results themselves contain sensitive data, which is a data governance issue rather than a tool risk.

From the tool's definition Tool name 'fleet_get_query_results' indicates retrieval of query results with no modification capability. No description provided, but the name and pattern of sibling tools (fleet_create_query, fleet_cancel_query) suggest this is a read-only retrieval…

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

POLICY

How to control fleet_get_query_results

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fleet_get_query_results": {}
  }
}

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

Create a free account and register Fleet — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Fleet tools

Destructive fleet_delete_bootstrap_package fleet_delete_bootstrap_package Destructive fleet_delete_custom_variable fleet_delete_custom_variable Destructive fleet_delete_host fleet_delete_host Destructive fleet_delete_mdm_profile fleet_delete_mdm_profile Destructive fleet_delete_query Delete a saved query from Fleet. Destructive fleet_delete_script Delete a script. Destructive fleet_delete_setup_assistant fleet_delete_setup_assistant Destructive fleet_unenroll_host_mdm fleet_unenroll_host_mdm

All 85 Fleet tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about fleet_get_query_results

What does the fleet_get_query_results tool do? +

fleet_get_query_results. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fleet_get_query_results? +

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

What risk level is fleet_get_query_results? +

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

Can I rate-limit fleet_get_query_results? +

Yes. Add a rate_limit block to the fleet_get_query_results 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 fleet_get_query_results completely? +

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

fleet_get_query_results is provided by the Fleet MCP server (fleet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fleet tool call.

Start from Fleet, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →