Resumes protection for one or multiple locations in Falcon Guard that were previously paused. You must provide either guardKey or placeId (or both). Use listLocalFalconGuardReports to find guard_key values for paused locations.
AI agents use resumeFalconGuardProtection 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.
The tool modifies the configuration state of Falcon Guard protection by changing paused locations to active/resumed status. This is reversible (protection can be paused again), so it qualifies as Write rather than Execute or Destructive.
From the tool's definition Tool name 'resumeFalconGuardProtection' and description 'Resumes protection...that were previously paused' indicates modification of protection status for locations. This is a state change operation that affects monitoring/protection settings.
Documented attack patterns abuse exactly the kind of access resumeFalconGuardProtection 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 resumeFalconGuardProtection:
{
"version": "1",
"default": "deny",
"tools": {
"resumeFalconGuardProtection": {
"limits": [
{
"counter": "resumefalconguardprotection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} resumeFalconGuardProtection 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.
Resumes protection for one or multiple locations in Falcon Guard that were previously paused. You must provide either guardKey or placeId (or both). Use listLocalFalconGuardReports to find guard_key values for paused locations. 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 resumeFalconGuardProtection: 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.
resumeFalconGuardProtection 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 resumeFalconGuardProtection 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 resumeFalconGuardProtection. 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.
resumeFalconGuardProtection 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.