detection.tradecraft | PolicyLayer

WHAT IT DOES

What detection.tradecraft does on OPTIX: Operational Platform for Threat Intelligence Exploration

AI agents invoke detection.tradecraft to trigger actions in OPTIX: Operational Platform for Threat Intelligence Exploration. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why detection.tradecraft needs a policy

This tool generates and likely executes or dispatches SIEM queries against live security infrastructure. 'Generate a SIEM threat hunting query' implies constructing and running queries against a SIEM platform, which constitutes executing operations whose effects depend on arguments.

From the tool's definition Generate a SIEM threat hunting query covering the complete known tradecraft

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

detection.tradecraft Rate-limited

detection.tradecraft stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "detection.tradecraft": {
      "limits": [
        {
          "counter": "detection.tradecraft_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OPTIX: Operational Platform for Threat Intelligence Exploration, so you can run agents against it safely.

FAQ

Questions about detection.tradecraft

What does the detection.tradecraft tool do? +

Generate a SIEM threat hunting query covering the complete known tradecraft. It is categorised as a Execute tool in the OPTIX: Operational Platform for Threat Intelligence Exploration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on detection.tradecraft? +

Register the OPTIX: Operational Platform for Threat Intelligence Exploration MCP server in PolicyLayer and add a rule for detection.tradecraft: 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 OPTIX: Operational Platform for Threat Intelligence Exploration. Nothing to install.

What risk level is detection.tradecraft? +

detection.tradecraft is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit detection.tradecraft? +

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

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

detection.tradecraft is provided by the OPTIX: Operational Platform for Threat Intelligence Exploration MCP server (AdamWaldie/OPTIX-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.