List dirty open buffers currently owned by an agent, with optional buffer-vs-disk diffs.
AI agents call get_dirty_owned_files to retrieve information from Vigentic MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports state information about dirty (modified) buffers and their diffs without creating, modifying, deleting, or executing any operations. It is purely informational and has no side effects on the filesystem or data. The confidence is high because the description clearly uses query language ('list', 'diffs') typical of Read operations.
From the tool's definition Tool name is 'get_dirty_owned_files' and description states it 'List[s] dirty open buffers currently owned by an agent, with optional buffer-vs-disk diffs.' The verb 'list' and the retrieval of status information about buffers indicate a read-only operation…
Attacks that exploit this kind of access
List dirty open buffers currently owned by an agent, with optional buffer-vs-disk diffs. It is categorised as a Read tool in the Vigentic MCP MCP Server, which means it retrieves data without modifying state.
Register the Vigentic MCP server in PolicyLayer and add a rule for get_dirty_owned_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 Vigentic MCP. Nothing to install.
get_dirty_owned_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 get_dirty_owned_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 get_dirty_owned_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.
get_dirty_owned_files is provided by the Vigentic MCP server (munozu/vigentic-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 →