Query TAK entities within a geographic area using point-radius or polygon
AI agents call tak_spatial_query to retrieve information from TAK Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries geographic entities and returns data without modifying state, executing code, or causing side effects. It is a straightforward read operation on geospatial data within a tactical awareness system. The low severity reflects minimal blast radius if misused—an attacker could discover entity locations but cannot alter state or trigger actions directly.
From the tool's definition Tool name 'tak_spatial_query' and description 'Query TAK entities within a geographic area' indicate a retrieval operation. No mention of modification, deletion, execution, or financial effects.
Documented attack patterns abuse exactly the kind of access tak_spatial_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TAK Server MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for tak_spatial_query:
{
"version": "1",
"default": "deny",
"tools": {
"tak_spatial_query": {}
}
}tak_spatial_query 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.
Query TAK entities within a geographic area using point-radius or polygon. It is categorised as a Read tool in the TAK Server MCP MCP Server, which means it retrieves data without modifying state.
Register the TAK Server MCP server in PolicyLayer and add a rule for tak_spatial_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 TAK Server MCP. Nothing to install.
tak_spatial_query 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 tak_spatial_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 tak_spatial_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.
tak_spatial_query is provided by the TAK Server MCP server (jfuginay/tak-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TAK Server MCP, 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.
11 TAK Server MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.