Full-text search across cached evidence titles and bodies, ordered by relevance (BM25). Optional
AI agents call search_work_context to retrieve information from Slopweaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search/query operation that retrieves and ranks cached data without side effects. It does not create, modify, delete, or execute any operations. The optional nature of parameters and the focus on searching and ordering results confirm this is purely a Read operation with minimal security risk.
From the tool's definition Tool performs 'Full-text search across cached evidence titles and bodies, ordered by relevance (BM25)'. The description explicitly indicates retrieval and ranking of existing data with no modification or deletion capabilities.
Attacks that exploit this kind of access
Full-text search across cached evidence titles and bodies, ordered by relevance (BM25). Optional. It is categorised as a Read tool in the Slopweaver MCP Server, which means it retrieves data without modifying state.
Register the Slopweaver MCP server in PolicyLayer and add a rule for search_work_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 Slopweaver. Nothing to install.
search_work_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 search_work_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 search_work_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.
search_work_context is provided by the Slopweaver MCP server (slopweaver/slopweaver). 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 →