Check whether a given filesystem path exists and is a git repository.
AI agents call validate_repo_path to retrieve information from Agentic Bits Claude Plugin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check of filesystem paths and git repository metadata. It has no side effects, does not execute code, does not modify data, and does not delete or move anything.
From the tool's definition Tool name 'validate_repo_path' and description 'Check whether a given filesystem path exists and is a git repository' indicate a query operation that retrieves status information about the filesystem and git repository state without modifying or executing…
Attacks that exploit this kind of access
Check whether a given filesystem path exists and is a git repository. It is categorised as a Read tool in the Agentic Bits Claude Plugin MCP Server, which means it retrieves data without modifying state.
Register the Agentic Bits Claude Plugin MCP server in PolicyLayer and add a rule for validate_repo_path: 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 Agentic Bits Claude Plugin. Nothing to install.
validate_repo_path 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 validate_repo_path 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 validate_repo_path. 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.
validate_repo_path is provided by the Agentic Bits Claude Plugin MCP server (onesmartguy/agentic-bits-claude-plugin). 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 →