Project-type intelligence: pass a project_type (restaurant, clinic, banking, construction, real_estate, residential_development, fitness, legal, retail, auto, etc.) and get L1 ZIPs ranked by market or residential opportunity score plus L2 matching verified businesses already operating in that sec...
Part of the Local Intel server.
Free to start. No card required.
AI agents invoke local_intel_project to trigger processes or run actions in Local Intel. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
local_intel_project can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"local_intel_project": {
"limits": [
{
"counter": "local_intel_project_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Local Intel policy for all 27 tools.
These attack patterns abuse exactly the kind of access local_intel_project gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Project-type intelligence: pass a project_type (restaurant, clinic, banking, construction, real_estate, residential_development, fitness, legal, retail, auto, etc.) and get L1 ZIPs ranked by market or residential opportunity score plus L2 matching verified businesses already operating in that sector. Returns sector gap counts, HHI, population, growth state, and new-build %. Best tool for site selection and franchise expansion when you know the business type but not the ZIP.. It is categorised as a Execute tool in the Local Intel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Local Intel MCP server in PolicyLayer and add a rule for local_intel_project: 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 Intel. Nothing to install.
local_intel_project 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 local_intel_project 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 local_intel_project. 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.
local_intel_project is provided by the Local Intel MCP server (https://gsb-swarm-production.up.railway.app/api/local-intel/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Local Intel tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.