List files changed vs a git base ref, filtered by glob patterns.
AI agents call tdd_changed_files to retrieve information from Promethean OS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about file changes in a git repository by comparing against a base reference. It filters results using glob patterns but performs no modifications, deletions, or code execution. This is a pure read operation with no destructive or operational side effects. Severity is low as misuse would only expose information about repository structure and change history.
From the tool's definition Tool name 'tdd_changed_files' and description 'List files changed vs a git base ref, filtered by glob patterns' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List files changed vs a git base ref, filtered by glob patterns. It is categorised as a Read tool in the Promethean OS MCP MCP Server, which means it retrieves data without modifying state.
Register the Promethean OS MCP server in PolicyLayer and add a rule for tdd_changed_files: 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 Promethean OS MCP. Nothing to install.
tdd_changed_files 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 tdd_changed_files 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 tdd_changed_files. 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.
tdd_changed_files is provided by the Promethean OS MCP server (octave-commons/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 →