AI agents call test_youtube_credentials to retrieve information from PersonalizationMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears designed to validate whether stored YouTube API credentials are functional by making a test API call. It retrieves or queries credential status without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—at worst, an attacker could confirm whether credentials are valid, but cannot access user data (that would be a separate tool) or modify anything.
From the tool's definition Tool name 'test_youtube_credentials' and description 'Test YouTube API credentials' indicate validation/verification of credentials without modifying data or triggering external actions. Testing credentials is a read-only verification operation.
Documented attack patterns abuse exactly the kind of access test_youtube_credentials gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PersonalizationMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for test_youtube_credentials:
{
"version": "1",
"default": "deny",
"tools": {
"test_youtube_credentials": {}
}
}test_youtube_credentials is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test YouTube API credentials. It is categorised as a Read tool in the PersonalizationMCP MCP Server, which means it retrieves data without modifying state.
Register the Personalization MCP server in PolicyLayer and add a rule for test_youtube_credentials: 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 PersonalizationMCP. Nothing to install.
test_youtube_credentials 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 test_youtube_credentials 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 test_youtube_credentials. 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.
test_youtube_credentials is provided by the Personalization MCP server (yangliangwei/personalizationmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 PersonalizationMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 PersonalizationMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.