Show repo-scoped open buffers, dirty state, current buffer, and changed ticks in one response.
AI agents call workspace_status 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 queries and displays the state of open buffers and their metadata without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns status information. No side effects or irreversible actions are possible. Severity is low because misuse would only expose code state information to an AI agent, not enable harmful modifications or execution.
From the tool's definition Tool description: 'Show repo-scoped open buffers, dirty state, current buffer, and changed ticks in one response.' The verb 'show' and the action of querying/displaying buffer status without modification indicates data retrieval only.
Attacks that exploit this kind of access
Show repo-scoped open buffers, dirty state, current buffer, and changed ticks in one response. 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 workspace_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 Vigentic MCP. Nothing to install.
workspace_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 workspace_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 workspace_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.
workspace_status 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 →