AI agents call get_contact_attributes to retrieve information from Spaceship without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact information (tax IDs, company registration numbers, etc.) with no side effects. It is a data lookup operation that poses minimal risk if misused by an AI agent; the worst outcome is information disclosure of data already in the system. No financial, destructive, or executable operations are involved.
From the tool's definition Tool description explicitly states 'Retrieve stored contact attributes' — a read-only operation that queries existing contact data without modification, deletion, or external execution.
Attacks that exploit this kind of access
Retrieve stored contact attributes for a specific contact (TLD-specific extra fields like tax IDs and company registration numbers). It is categorised as a Read tool in the Spaceship MCP Server, which means it retrieves data without modifying state.
Register the Spaceship MCP server in PolicyLayer and add a rule for get_contact_attributes: 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.
get_contact_attributes 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_contact_attributes 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_contact_attributes. 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_contact_attributes 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 →