Manually triggers a campaign to run immediately. COSTS CREDITS — the total credits required will be checked against your available credits. Use listLocalFalconCampaignReports to find the campaign_key for the campaign you want to run. IMPORTANT: Campaign runs trigger multiple scans and can take mi...
AI agents invoke runLocalFalconCampaign to trigger actions in Local Falcon MCP Server. 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.
This tool executes an external operation (campaign run) whose effects depend on the campaign configuration and parameters. While it has a financial dimension (credit consumption), the primary action is triggering an operation whose side effects are significant and depend on execution context.
From the tool's definition Tool description states it 'Manually triggers a campaign to run immediately' and 'COSTS CREDITS — the total credits required will be checked against your available credits.' The tool initiates external operations (campaign scans) that 'can take minutes to…
Documented attack patterns abuse exactly the kind of access runLocalFalconCampaign 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 runLocalFalconCampaign:
{
"version": "1",
"default": "deny",
"tools": {
"runLocalFalconCampaign": {
"limits": [
{
"counter": "runlocalfalconcampaign_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}runLocalFalconCampaign 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.
Free to start. No card required.
Manually triggers a campaign to run immediately. COSTS CREDITS — the total credits required will be checked against your available credits. Use listLocalFalconCampaignReports to find the campaign_key for the campaign you want to run. IMPORTANT: Campaign runs trigger multiple scans and can take minutes to hours to complete depending on the number of locations and keywords. If the response says. It is categorised as a Execute tool in the Local Falcon MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Local Falcon MCP Server MCP server in PolicyLayer and add a rule for runLocalFalconCampaign: 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.
runLocalFalconCampaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the runLocalFalconCampaign 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 runLocalFalconCampaign. 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.
runLocalFalconCampaign 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.