Get the per-domain email signature settings (mode, position, html). Returns mode=
AI agents call get_domain_signature to retrieve information from TrekMail MCP Server 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 email signature configuration settings with no side effects. It is a read-only operation that fetches existing data without creating, modifying, or deleting anything. The low severity reflects minimal risk even if misused—an agent accessing signature settings poses no blast radius for data loss, financial impact, or service disruption.
From the tool's definition Tool name is 'get_domain_signature' and description states 'Get the per-domain email signature settings' with no modification, creation, or deletion capability. Returns only signature configuration data.
Attacks that exploit this kind of access
Get the per-domain email signature settings (mode, position, html). Returns mode=. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for get_domain_signature: 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 TrekMail MCP Server. Nothing to install.
get_domain_signature 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_domain_signature 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_domain_signature. 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_domain_signature is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). 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 →