vector_store_add
AI agents use vector_store_add to create or update resources in Vending Machine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vending Machine environment.
The tool performs a write operation by adding entries to a vector store, which creates or modifies data. This is reversible (items can typically be removed later), so it does not qualify as Destructive.
From the tool's definition Tool name 'vector_store_add' indicates it adds data to a vector store. The description is empty, limiting direct evidence, but the naming pattern and the server's context (managing vector stores) suggests a data modification operation.
Attacks that exploit this kind of access
vector_store_add. It is categorised as a Write tool in the Vending Machine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vending Machine MCP server in PolicyLayer and add a rule for vector_store_add: 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 Vending Machine. Nothing to install.
vector_store_add 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 vector_store_add 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 vector_store_add. 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.
vector_store_add is provided by the Vending Machine MCP server (yokiidesu/vending-machine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
vector_store_add is one line of Vending Machine's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →