Retrieve contact information (emails) for an Instagram creator.
AI agents call instagram_get_contact to retrieve information from CreatorDB 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 contact information (emails) for creators—a read-only operation that queries and returns existing data without side effects. However, severity is elevated to 'medium' rather than 'low' because contact information is sensitive PII that could be misused for spam, social engineering, harassment, or unauthorized outreach if an AI agent gains access and operates without proper safeguards.
From the tool's definition Tool name 'instagram_get_contact' and description 'Retrieve contact information (emails) for an Instagram creator' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Retrieve contact information (emails) for an Instagram creator. It is categorised as a Read tool in the CreatorDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CreatorDB MCP Server MCP server in PolicyLayer and add a rule for instagram_get_contact: 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 CreatorDB MCP Server. Nothing to install.
instagram_get_contact 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 instagram_get_contact 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 instagram_get_contact. 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.
instagram_get_contact is provided by the CreatorDB MCP Server MCP server (saiyamvora13/creatordb-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 →