Inspect a workspace.
AI agents call knowledge_workspace_status to retrieve information from Chisel Knowledge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs inspection/querying of workspace state with no side effects. It falls squarely within the Read category as it retrieves or queries data about a workspace's status. Low severity because workspace status inspection poses minimal risk—it does not modify data, execute code, delete anything, or trigger external operations.
From the tool's definition Tool name 'knowledge_workspace_status' and description 'Inspect a workspace' indicate a read-only operation that retrieves status information about an existing workspace without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Inspect a workspace. It is categorised as a Read tool in the Chisel Knowledge MCP MCP Server, which means it retrieves data without modifying state.
Register the Chisel Knowledge MCP server in PolicyLayer and add a rule for knowledge_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 Chisel Knowledge MCP. Nothing to install.
knowledge_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 knowledge_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 knowledge_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.
knowledge_workspace_status is provided by the Chisel Knowledge MCP server (teknologika/chisel-knowledge-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 →