Purpose: Retrieve the existing TipTap JSON content of a broadcast or template, optionally bundled with the TipTap schema reference. Also connects the agent to the editor so the avatar is visible while content is being generated. When to use: - Always call this before compose-broadcast or compose-...
AI agents call get-tiptap-json-content to retrieve information from Email Sending MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the current state of email content in TipTap JSON format. It has no side effects beyond fetching data and establishing a visual connection to an editor. While it mentions connecting to the editor for avatar visibility, this is a read-only contextual enhancement, not a write or execute operation.
From the tool's definition The tool description states it 'Retrieve[s] the existing TipTap JSON content' and 'Returns: The TipTap JSON'. The purpose explicitly identifies retrieval and inspection activities with no modification or side effects mentioned.
Documented attack patterns abuse exactly the kind of access get-tiptap-json-content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Email Sending MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-tiptap-json-content:
{
"version": "1",
"default": "deny",
"tools": {
"get-tiptap-json-content": {}
}
}get-tiptap-json-content 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.
Purpose: Retrieve the existing TipTap JSON content of a broadcast or template, optionally bundled with the TipTap schema reference. Also connects the agent to the editor so the avatar is visible while content is being generated. When to use: - Always call this before compose-broadcast or compose-template to fetch the current document state — even if you expect it to be empty, the resource may have content set via the dashboard - When the user asks to edit, tweak, or modify existing email content - To inspect the current TipTap structure of a resource Returns: The TipTap JSON content object for the resource, and optionally the TipTap schema. Use the content as the base for modifications, then pass the updated JSON to compose-broadcast or compose-template. Note: This tool automatically connects the agent to the editor. The subsequent compose-broadcast or compose-template call will disconnect when done. Tip: Set include_schema to true to get both the existing content and the schema in one call. It is categorised as a Read tool in the Email Sending MCP MCP Server, which means it retrieves data without modifying state.
Register the Email Sending MCP server in PolicyLayer and add a rule for get-tiptap-json-content: 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 Email Sending MCP. Nothing to install.
get-tiptap-json-content 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-tiptap-json-content 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-tiptap-json-content. 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-tiptap-json-content is provided by the Email Sending MCP server (resend/resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 77 Email Sending MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.