Send a Cursor on Target (CoT) event to TAK Server
AI agents use tak_send_cot_event to create or update resources in TAK Server MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TAK Server MCP environment.
This tool sends (writes/creates) CoT events to TAK Server, which are tactical position reports or situational updates. While not destructive or financial, sending false or malicious CoT events could mislead tactical operations, trigger emergency responses, or disrupt coordination.
From the tool's definition Tool name 'tak_send_cot_event' and description 'Send a Cursor on Target (CoT) event to TAK Server' indicate the tool creates/transmits tactical data objects (CoT events) to a server.
Documented attack patterns abuse exactly the kind of access tak_send_cot_event 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_send_cot_event:
{
"version": "1",
"default": "deny",
"tools": {
"tak_send_cot_event": {
"limits": [
{
"counter": "tak_send_cot_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} tak_send_cot_event stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a Cursor on Target (CoT) event to TAK Server. It is categorised as a Write tool in the TAK Server MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TAK Server MCP server in PolicyLayer and add a rule for tak_send_cot_event: 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_send_cot_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tak_send_cot_event 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_send_cot_event. 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_send_cot_event 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.