Call a request registered to a vendor. Args: vendor_name: Name of the vendor to use request_type: The request type to call request_data: Additional data to pass to the request Returns: Response data from the vendor request
AI agents invoke call_vendor_request to trigger actions in OBS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary vendor-registered requests in OBS with user-supplied request type and data. Since vendor requests are plugin-defined and can perform a wide range of operations (including potentially destructive or state-changing actions), this falls under Execute.
From the tool's definition 'Call a request registered to a vendor' with arbitrary 'request_type' and 'request_data' parameters passed to external vendor plugins
Documented attack patterns abuse exactly the kind of access call_vendor_request 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 call_vendor_request:
{
"version": "1",
"default": "deny",
"tools": {
"call_vendor_request": {
"limits": [
{
"counter": "call_vendor_request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}call_vendor_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Call a request registered to a vendor. Args: vendor_name: Name of the vendor to use request_type: The request type to call request_data: Additional data to pass to the request Returns: Response data from the vendor request. It is categorised as a Execute tool in the OBS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OBS MCP Server MCP server in PolicyLayer and add a rule for call_vendor_request: 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.
call_vendor_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_vendor_request 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 call_vendor_request. 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.
call_vendor_request 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.