Create a new FileSearch store for semantic code search.
AI agents use create_file_store to create or update resources in Gpal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gpal environment.
This tool creates a new data structure (a FileSearch store) for indexing code. While creation is a Write-class operation, the severity is medium rather than low because misconfiguration or resource exhaustion could degrade system performance or consume storage. It is reversible (the store can be deleted), so it does not rise to Destructive. No code execution, financial impact, or irreversible data loss is involved.
From the tool's definition Tool is named 'create_file_store' and described as 'Create a new FileSearch store for semantic code search.' The verb 'create' indicates data creation/initialization, which is reversible.
Documented attack patterns abuse exactly the kind of access create_file_store gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gpal, and nothing reaches the server without passing your rules. This is the rule we recommend for create_file_store:
{
"version": "1",
"default": "deny",
"tools": {
"create_file_store": {
"limits": [
{
"counter": "create_file_store_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_file_store 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.
Create a new FileSearch store for semantic code search. It is categorised as a Write tool in the Gpal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gpal MCP server in PolicyLayer and add a rule for create_file_store: 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 Gpal. Nothing to install.
create_file_store 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 create_file_store 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 create_file_store. 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.
create_file_store is provided by the Gpal MCP server (tobert/gpal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gpal, 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.
19 Gpal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.