Returns the instructional body for a cold-start mega-audit: a 1M-context-friendly orchestration that pulls 90 days of history from every connected MCP server in one pass and populates the AI work console (core-profile, team-directory, work files, voice rules). Pair with
AI agents call start_mega_audit 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 retrieves and aggregates historical data from connected MCP servers (GitHub, Slack, etc.) and populates internal profile/console structures. The primary action is reading/fetching data across a wide surface area. 'Populates' suggests some write-side effects to local profile structures, but the description frames this as an orchestration that returns instructional body, suggesting it coordinates reads.
From the tool's definition 'pulls 90 days of history from every connected MCP server in one pass and populates the AI work console (core-profile, team-directory, work files, voice rules)'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Returns the instructional body for a cold-start mega-audit: a 1M-context-friendly orchestration that pulls 90 days of history from every connected MCP server in one pass and populates the AI work console (core-profile, team-directory, work files, voice rules). Pair with. 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_mega_audit: 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_mega_audit 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_mega_audit 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_mega_audit. 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_mega_audit 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 →