Sends a message to an active Jules session.
AI agents use jules_send_message to create or update resources in Jules MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jules MCP Server environment.
This tool sends a message to an existing session, which is a write operation. It creates/posts new data (a message) to an active session. While it could potentially trigger AI actions depending on the message content, the primary action described is sending a message, not executing code or commands directly.
From the tool's definition Sends a message to an active Jules session
Attacks that exploit this kind of access
Sends a message to an active Jules session. It is categorised as a Write tool in the Jules MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jules MCP Server MCP server in PolicyLayer and add a rule for jules_send_message: 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 Jules MCP Server. Nothing to install.
jules_send_message 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 jules_send_message 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 jules_send_message. 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.
jules_send_message is provided by the Jules MCP Server MCP server (streetquant/jules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
jules_send_message is one line of Jules MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →