Reply to a message. Automatically sets subject, thread, and in-reply-to headers.
AI agents use keyid_reply to create or update resources in KeyID Agent Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KeyID Agent Kit environment.
This tool sends an email reply, which creates new outbound email data. It is a write operation (composing and sending a message) with moderate blast radius — an AI agent could send unwanted replies to arbitrary threads, potentially leaking information or causing reputational harm, but it is reversible in the sense that the action is bounded to a single message send.
From the tool's definition Reply to a message. Automatically sets subject, thread, and in-reply-to headers.
Attacks that exploit this kind of access
Reply to a message. Automatically sets subject, thread, and in-reply-to headers. It is categorised as a Write tool in the KeyID Agent Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KeyID Agent Kit MCP server in PolicyLayer and add a rule for keyid_reply: 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 KeyID Agent Kit. Nothing to install.
keyid_reply 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 keyid_reply 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 keyid_reply. 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.
keyid_reply is provided by the KeyID Agent Kit MCP server (keyid-ai/agent-kit). 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 →