Speak text using browser text-to-speech. Automatically starts browser interface if not running.
AI agents invoke speak to trigger actions in Jarvis MCP. 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 triggers an external operation (text-to-speech audio output via the browser) and can automatically launch a browser interface. It doesn't just read or write data — it executes an action in the browser environment. The blast radius is low since it only produces audio output and starts a UI, but misuse could involve unwanted audio playback or unsolicited browser launches.
From the tool's definition 'Speak text using browser text-to-speech. Automatically starts browser interface if not running.'
Documented attack patterns abuse exactly the kind of access speak 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 speak:
{
"version": "1",
"default": "deny",
"tools": {
"speak": {
"limits": [
{
"counter": "speak_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}speak 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.
Speak text using browser text-to-speech. Automatically starts browser interface if not running. It is categorised as a Execute tool in the Jarvis MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jarvis MCP server in PolicyLayer and add a rule for speak: 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.
speak 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 speak 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 speak. 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.
speak 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.