AI agents use set_email_protection to create or update resources in Spaceship — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spaceship environment.
This tool modifies domain configuration by enabling or disabling email protection (contact form display). While reversible, this is a Write operation as it alters domain settings. The severity is medium because misconfiguration could expose or hide contact information unintentionally, affecting domain functionality and communications, but it does not destroy data or move money.
From the tool's definition The tool name 'set_email_protection' combined with the description 'Toggle the contact form display for a domain' indicates a state change operation. 'Toggle' and 'set' are modification verbs that create reversible configuration changes to domain settings.
Attacks that exploit this kind of access
Toggle the contact form display for a domain. It is categorised as a Write tool in the Spaceship MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spaceship MCP server in PolicyLayer and add a rule for set_email_protection: 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 Spaceship. Nothing to install.
set_email_protection 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 set_email_protection 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 set_email_protection. 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.
set_email_protection is provided by the Spaceship MCP server (naveenkm007/spaceship-mcp). 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 →