get_pinterest_pins
AI agents call get_pinterest_pins to retrieve information from Mcp Metricool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Pinterest pin data with no indication of modification, deletion, or execution capabilities. It aligns with the Read category as a query/fetch operation. Confidence is 0.85 rather than higher because the tool description is empty, leaving minor ambiguity, but the naming pattern and server context strongly suggest read-only retrieval.
From the tool's definition Tool name 'get_pinterest_pins' follows the retrieval pattern of sibling tools (get_bluesky_posts, get_instagram_posts, get_facebook_posts, etc.). The 'get_' prefix consistently indicates data retrieval across all tools on this server.
Attacks that exploit this kind of access
get_pinterest_pins. It is categorised as a Read tool in the Mcp Metricool MCP Server, which means it retrieves data without modifying state.
Register the Mcp Metricool MCP server in PolicyLayer and add a rule for get_pinterest_pins: 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 Mcp Metricool. Nothing to install.
get_pinterest_pins 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_pinterest_pins 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_pinterest_pins. 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_pinterest_pins is provided by the Mcp Metricool MCP server (namdzmaso02/mcp-metricool). 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 →