Get the full configuration of a specific campaign including start/end dates and injected rules.
AI agents call get_campaign to retrieve information from NeuronSearchLab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries campaign configuration metadata without modifying, deleting, or executing external operations. It has no side effects on campaign state or data. While campaign configurations may contain sensitive information (rules, dates), the read-only nature and lack of irreversible or dangerous operations place it in the Read category with low severity.
From the tool's definition Tool name is 'get_campaign' and description states 'Get the full configuration of a specific campaign' — the verb 'Get' and the absence of any modification language (create, update, delete) indicate retrieval only.
Attacks that exploit this kind of access
Get the full configuration of a specific campaign including start/end dates and injected rules. It is categorised as a Read tool in the NeuronSearchLab MCP Server, which means it retrieves data without modifying state.
Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for get_campaign: 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 NeuronSearchLab. Nothing to install.
get_campaign 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 get_campaign 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 get_campaign. 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.
get_campaign is provided by the NeuronSearchLab MCP server (neuronsearchlab/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →