Get pending voice input from users (auto-delivered by default)
AI agents call get_voice_input to retrieve information from Jarvis MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pending voice input data from users with no side effects, reversible operations, code execution, destructive actions, or financial implications. It is a straightforward data retrieval operation, making it a Read category tool with low severity since the blast radius of misuse (reading user voice input) is limited compared to tools that execute code or modify systems.
From the tool's definition Tool name 'get_voice_input' and description 'Get pending voice input from users' indicate retrieval of data without modification or execution of commands. The action is read-only—it retrieves or queries user input that has already been captured.
Documented attack patterns abuse exactly the kind of access get_voice_input gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jarvis MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_voice_input:
{
"version": "1",
"default": "deny",
"tools": {
"get_voice_input": {}
}
}get_voice_input is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get pending voice input from users (auto-delivered by default). It is categorised as a Read tool in the Jarvis MCP MCP Server, which means it retrieves data without modifying state.
Register the Jarvis MCP server in PolicyLayer and add a rule for get_voice_input: 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 Jarvis MCP. Nothing to install.
get_voice_input is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_voice_input 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 get_voice_input. 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.
get_voice_input is provided by the Jarvis MCP server (shantur/jarvis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Jarvis MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Jarvis MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.