Low Risk

get_campaign_by_name

根據名稱獲取行動資訊

How to control get_campaign_by_name ↓

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

Low Risk

This tool retrieves campaign information from an OpenCTI threat intelligence database without modifying, executing, or deleting data. It is a simple lookup/query operation with no side effects, fitting the 'Read' category. The blast radius of misuse is minimal—an agent could query campaigns but cannot cause damage, financial loss, or code execution.

From the tool's definition Tool name 'get_campaign_by_name' and description indicate data retrieval. The description translates to 'Get campaign information by name', which is a query operation.

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

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

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

get_campaign_by_name 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 OpenCTI 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.

Go deeper

What does the get_campaign_by_name tool do? +

根據名稱獲取行動資訊. It is categorised as a Read tool in the OpenCTI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_campaign_by_name? +

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

What risk level is get_campaign_by_name? +

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

Can I rate-limit get_campaign_by_name? +

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

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

get_campaign_by_name is provided by the OpenCTI MCP Server MCP server (zxzinn/opencti-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenCTI MCP Server tool call.

Deterministic rules across all 16 OpenCTI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

16 OpenCTI MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.