Returns the instructional body for a weekly retro over the last 7 days of activity: pull evidence via catch_me_up + search_work_context, identify shifts in priorities/stakeholders/open loops, and propose 1-2 follow-ups. Returns the retro inline; only persists if work-console write tools are prese...
AI agents call start_retro 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.
The tool primarily retrieves and aggregates activity data (via catch_me_up and search_work_context) and returns analysis inline. It may optionally persist output if write tools are present, but its core function is read/query. The conditional persistence lowers confidence slightly, but the default behavior is read-only retrieval and summarization.
From the tool's definition Returns the instructional body for a weekly retro over the last 7 days of activity: pull evidence via catch_me_up + search_work_context... Returns the retro inline; only persists if work-console write tools are present.
Attacks that exploit this kind of access
Returns the instructional body for a weekly retro over the last 7 days of activity: pull evidence via catch_me_up + search_work_context, identify shifts in priorities/stakeholders/open loops, and propose 1-2 follow-ups. Returns the retro inline; only persists if work-console write tools are present. Designed for a Sunday-evening run. 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 start_retro: 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.
start_retro 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 start_retro 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 start_retro. 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.
start_retro 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 →