Transcribe audio. Fetches the URL server-side and forwards as multipart/form-data file upload.${X402_OK}
AI agents invoke venice_asr to trigger actions in Venice 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 fetches a URL server-side (external network request) and uploads data to an external API endpoint. It triggers external operations — fetching remote content and performing an API call — making it Execute rather than a simple Read. Severity is medium because it involves outbound network requests to arbitrary URLs and data forwarding to Venice's API.
From the tool's definition Transcribe audio. Fetches the URL server-side and forwards as multipart/form-data file upload.
Documented attack patterns abuse exactly the kind of access venice_asr gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Venice MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for venice_asr:
{
"version": "1",
"default": "deny",
"tools": {
"venice_asr": {
"limits": [
{
"counter": "venice_asr_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} venice_asr 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.
Transcribe audio. Fetches the URL server-side and forwards as multipart/form-data file upload.${X402_OK}. It is categorised as a Execute tool in the Venice MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Venice MCP Server MCP server in PolicyLayer and add a rule for venice_asr: 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 Venice MCP Server. Nothing to install.
venice_asr 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 venice_asr 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 venice_asr. 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.
venice_asr is provided by the Venice MCP Server MCP server (veniceai/venice-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Venice MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
27 Venice MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.