streamfog_set_lens
AI agents use streamfog_set_lens to create or update resources in Streamfog MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Streamfog MCP environment.
Based on the tool name and server context, this tool likely sets or applies a specific AR lens/filter to the stream, which is a write/modify operation with reversible effects. Confidence is low because the description is empty, so classification relies solely on naming conventions and sibling tool context.
From the tool's definition Tool name 'streamfog_set_lens' and sibling tools context (streamfog_list_lenses, streamfog_toggle_avatar, streamfog_clear_effects) suggest it sets/applies an AR lens or face filter to a live OBS stream.
Attacks that exploit this kind of access
streamfog_set_lens. It is categorised as a Write tool in the Streamfog MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Streamfog MCP server in PolicyLayer and add a rule for streamfog_set_lens: 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_set_lens is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the streamfog_set_lens 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_set_lens. 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_set_lens 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 →