Saves a screenshot of a source to a file. Args: source_name: Name of the source to get a screenshot of file_path: Path to save the screenshot to image_format: Image format (png, jpeg, bmp, tga, gif) image_width: Screenshot width (0 = source width) image_height: Screenshot height (0 = source heigh...
AI agents use save_source_screenshot to create or update resources in OBS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OBS MCP Server environment.
This tool creates and writes image files to disk, which is a reversible modification of the filesystem. It does not execute arbitrary code, delete data, or move money. The severity is medium rather than low because an agent could be tricked into writing files to sensitive locations or filling disk space, though the impact is still reversible (files can be deleted).
From the tool's definition The tool "saves a screenshot of a source to a file" — it creates a new file on the filesystem with image data at a user-specified file_path. This is a write operation that modifies the local filesystem by creating new data.
Documented attack patterns abuse exactly the kind of access save_source_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OBS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for save_source_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"save_source_screenshot": {
"limits": [
{
"counter": "save_source_screenshot_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_source_screenshot stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Saves a screenshot of a source to a file. Args: source_name: Name of the source to get a screenshot of file_path: Path to save the screenshot to image_format: Image format (png, jpeg, bmp, tga, gif) image_width: Screenshot width (0 = source width) image_height: Screenshot height (0 = source height) image_compression_quality: Compression quality (1-100, -1 = default) Returns: Path to the saved screenshot. It is categorised as a Write tool in the OBS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OBS MCP Server MCP server in PolicyLayer and add a rule for save_source_screenshot: 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 OBS MCP Server. Nothing to install.
save_source_screenshot 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 save_source_screenshot 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 save_source_screenshot. 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.
save_source_screenshot is provided by the OBS MCP Server MCP server (royshil/obs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 200 OBS MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
200 OBS MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.