Adds one or multiple locations to be protected by Falcon Guard. Each business location must already be added to your Saved Locations in your Local Falcon dashboard before it can be protected. Use listAllLocalFalconLocations to verify locations exist first.
AI agents use addLocationsToFalconGuard 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 or modifies a configuration state (which locations are protected by Falcon Guard) reversibly—locations can presumably be removed later. It does not retrieve data (Read), execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). The modification is reversible, placing it in the Write category.
From the tool's definition The tool 'addLocationsToFalconGuard' performs a create/add operation that modifies the protected locations list in Falcon Guard.
Documented attack patterns abuse exactly the kind of access addLocationsToFalconGuard 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 addLocationsToFalconGuard:
{
"version": "1",
"default": "deny",
"tools": {
"addLocationsToFalconGuard": {
"limits": [
{
"counter": "addlocationstofalconguard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addLocationsToFalconGuard 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.
Adds one or multiple locations to be protected by Falcon Guard. Each business location must already be added to your Saved Locations in your Local Falcon dashboard before it can be protected. Use listAllLocalFalconLocations to verify locations exist first. 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 addLocationsToFalconGuard: 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.
addLocationsToFalconGuard 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 addLocationsToFalconGuard 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 addLocationsToFalconGuard. 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.
addLocationsToFalconGuard 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.