Show git status and the 5 most recent commits in the project on the HPC cluster.
AI agents call git_status to retrieve information from Tacc Mcp Bio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version control state and commit history without making changes, executing code, or triggering side effects. It is a straightforward read operation on git metadata. Severity is low because misuse (e.g., an agent invoking it repeatedly) poses no security risk beyond minor resource consumption.
From the tool's definition Tool shows git status and lists recent commits—purely informational queries with no modification or execution. The description explicitly indicates 'show' and 'in the project', indicating read-only inspection of version control metadata.
Attacks that exploit this kind of access
Show git status and the 5 most recent commits in the project on the HPC cluster. It is categorised as a Read tool in the Tacc Mcp Bio MCP Server, which means it retrieves data without modifying state.
Register the Tacc Mcp Bio MCP server in PolicyLayer and add a rule for git_status: 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 Tacc Mcp Bio. Nothing to install.
git_status 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 git_status 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 git_status. 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.
git_status is provided by the Tacc Mcp Bio MCP server (narasimhan-lab/tacc-mcp-bio). 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 →