AI agents call staged_preview to retrieve information from Fs Git without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Previewing staged changes is a read-only operation that shows what modifications are pending without applying, committing, or altering any data. It has no side effects and is analogous to 'git diff --staged'.
From the tool's definition Preview staged changes
Attacks that exploit this kind of access
Preview staged changes. It is categorised as a Read tool in the Fs Git MCP Server, which means it retrieves data without modifying state.
Register the Fs Git MCP server in PolicyLayer and add a rule for staged_preview: 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 Fs Git. Nothing to install.
staged_preview is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the staged_preview 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 staged_preview. 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.
staged_preview is provided by the Fs Git MCP server (wojons/fs-git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →