הוספת לקוח חדש
AI agents use add_customer to create or update resources in Stevia Store MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stevia Store MCP Server environment.
This tool creates a new customer entry in the database, which is a reversible Write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), process financial transactions (not Financial), or merely retrieve data (not Read).
From the tool's definition Tool name 'add_customer' and description 'הוספת לקוח חדש' (Hebrew: 'Add a new customer') indicate creation of a new customer record in the e-commerce system.
Attacks that exploit this kind of access
הוספת לקוח חדש. It is categorised as a Write tool in the Stevia Store MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stevia Store MCP Server MCP server in PolicyLayer and add a rule for add_customer: 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 Stevia Store MCP Server. Nothing to install.
add_customer 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 add_customer 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 add_customer. 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.
add_customer is provided by the Stevia Store MCP Server MCP server (yairbarak22/mcpserverstevia). 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 →