AI agents use jis_send_verified to create or update resources in Jis — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jis environment.
This tool writes/creates data (sends a message) with side effects that are reversible or recoverable. It does not execute arbitrary code, destroy data, or move money. The bilateral consent requirement mitigates severity somewhat, but message transmission—especially within a verification system—carries medium risk if an agent misuses it to send fraudulent or malicious verified messages to third parties.
From the tool's definition Tool name 'jis_send_verified' and description 'Send a JIS-verified message' indicate the tool creates/transmits a message. The requirement that 'bilateral intent acceptance' must occur first suggests reversibility and safeguards against unilateral action.
Attacks that exploit this kind of access
Send a JIS-verified message. Requires bilateral intent acceptance first. It is categorised as a Write tool in the Jis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jis MCP server in PolicyLayer and add a rule for jis_send_verified: 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 Jis. Nothing to install.
jis_send_verified 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 jis_send_verified 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 jis_send_verified. 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.
jis_send_verified is provided by the Jis MCP server (jaspertvdm/mcp-server-jis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →