AI agents call get_workspace_context to retrieve information from Blop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'Return' and the nature of the data returned (metadata, URIs, defaults) are purely informational with no side effects. This is a standard metadata query operation that fits the Read category. Severity is low because workspace context information typically contains only non-sensitive structural data needed for discovery and does not enable direct access to sensitive data or dangerous operations.
From the tool's definition Tool name 'get_workspace_context' and description 'Return compact workspace metadata, resource URIs, and discovery defaults' indicate retrieval of metadata and configuration information with no modification or execution.
Attacks that exploit this kind of access
Return compact workspace metadata, resource URIs, and discovery defaults. It is categorised as a Read tool in the Blop MCP Server, which means it retrieves data without modifying state.
Register the Blop MCP server in PolicyLayer and add a rule for get_workspace_context: 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 Blop. Nothing to install.
get_workspace_context 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_workspace_context 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_workspace_context. 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_workspace_context is provided by the Blop MCP server (n2400813g/blop-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 →