Creates a new campaign in Local Falcon. Campaigns allow you to schedule recurring scans for one or multiple locations with one or multiple keywords. Locations must already exist in your Saved Locations (use listAllLocalFalconLocations to verify).
AI agents use createLocalFalconCampaign to create or update resources in Local Falcon MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Falcon MCP Server environment.
This tool creates new campaign objects with persistent effects (scheduling recurring scans), which is reversible but represents a write operation that modifies user data and configuration. It does not execute arbitrary code, delete data, or involve financial transactions, placing it in the Write category.
From the tool's definition Tool description states it 'Creates a new campaign' in Local Falcon, which is a data creation operation that modifies the user's account state by adding a new campaign configuration.
Documented attack patterns abuse exactly the kind of access createLocalFalconCampaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Falcon MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for createLocalFalconCampaign:
{
"version": "1",
"default": "deny",
"tools": {
"createLocalFalconCampaign": {
"limits": [
{
"counter": "createlocalfalconcampaign_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createLocalFalconCampaign 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.
Creates a new campaign in Local Falcon. Campaigns allow you to schedule recurring scans for one or multiple locations with one or multiple keywords. Locations must already exist in your Saved Locations (use listAllLocalFalconLocations to verify). It is categorised as a Write tool in the Local Falcon MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Local Falcon MCP Server MCP server in PolicyLayer and add a rule for createLocalFalconCampaign: 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 Local Falcon MCP Server. Nothing to install.
createLocalFalconCampaign 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 createLocalFalconCampaign 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 createLocalFalconCampaign. 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.
createLocalFalconCampaign is provided by the Local Falcon MCP Server MCP server (local-falcon/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local Falcon MCP Server, 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.
37 Local Falcon MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.