Store visual analyses in ChromaDB vector base for future semantic retrieval.
AI agents use pinterest_ingest to create or update resources in Pinterest Vision — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pinterest Vision environment.
This tool writes/stores data (visual analyses) into a ChromaDB vector database. It creates new records in a persistent data store, which is a reversible write operation. It does not delete data, execute code, or involve financial transactions. Severity is medium because it modifies a shared vector database that could be polluted with bad data by a misusing agent, affecting downstream semantic retrieval quality.
From the tool's definition Store visual analyses in ChromaDB vector base for future semantic retrieval
Attacks that exploit this kind of access
Store visual analyses in ChromaDB vector base for future semantic retrieval. It is categorised as a Write tool in the Pinterest Vision MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pinterest Vision MCP server in PolicyLayer and add a rule for pinterest_ingest: 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 Pinterest Vision. Nothing to install.
pinterest_ingest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pinterest_ingest 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 pinterest_ingest. 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.
pinterest_ingest is provided by the Pinterest Vision MCP server (kreminskaya/pinterest-vision-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 →