Search across all entity types with initiative awareness
AI agents call search_workspace to retrieve information from Helios-9 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data across the workspace (projects, tasks, initiatives, documents) without creating, modifying, deleting, or executing any operations. It has no side effects and cannot alter system state. It is a straightforward read operation with minimal blast radius if misused by an AI agent—worst case being information disclosure of accessible workspace data.
From the tool's definition Tool name 'search_workspace' and description 'Search across all entity types' indicates data retrieval without modification. The function is explicitly a search operation, which is a read-only action that queries existing data without side effects.
Attacks that exploit this kind of access
Search across all entity types with initiative awareness. It is categorised as a Read tool in the Helios-9 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Helios-9 MCP Server MCP server in PolicyLayer and add a rule for search_workspace: 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 Helios-9 MCP Server. Nothing to install.
search_workspace 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 search_workspace 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 search_workspace. 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.
search_workspace is provided by the Helios-9 MCP Server MCP server (jakedx6/helios9-mcp-server). 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 →