Get contact information for a YouTube creator.
AI agents call youtube_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 (email, business inquiries address, etc.) for YouTube creators from the CreatorDB API. It performs a query operation with no reversible or irreversible modifications to data. While the retrieved contact information could be considered sensitive personal/business data, the tool itself is a passive read operation.
From the tool's definition Tool name 'youtube_get_contact' and description 'Get contact information for a YouTube creator' indicate retrieval of data with no modification or side effects.
Attacks that exploit this kind of access
Get contact information for a YouTube 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 youtube_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.
youtube_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 youtube_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 youtube_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.
youtube_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 →