streamfog_clear_effects
AI agents call streamfog_clear_effects to permanently remove resources in Streamfog MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The description is empty, so classification relies solely on the tool name. 'Clear' typically means removing/resetting all active effects, which could be considered irreversible (you can't undo a cleared live stream effect without re-applying). However, since effects can likely be re-applied, this could also be Write.
From the tool's definition Tool name 'streamfog_clear_effects' — the word 'clear' implies removing or wiping all active effects, which is likely irreversible in the context of a live stream state.
Attacks that exploit this kind of access
streamfog_clear_effects. It is categorised as a Destructive tool in the Streamfog MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Streamfog MCP server in PolicyLayer and add a rule for streamfog_clear_effects: 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 Streamfog MCP. Nothing to install.
streamfog_clear_effects is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the streamfog_clear_effects 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 streamfog_clear_effects. 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.
streamfog_clear_effects is provided by the Streamfog MCP server (sandraschi/streamfog-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 →