קבלת סיכום מכירות
AI agents call get_sales_summary to retrieve information from Stevia Store MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sales summary information for analytics purposes. It performs no write, execute, destructive, or financial operations—it only queries and returns existing sales data. The 'get_' prefix and summary retrieval nature confirm it is a Read category tool with low severity since unauthorized access to sales analytics, while potentially sensitive, does not enable direct harm or data loss.
From the tool's definition Tool name 'get_sales_summary' and description 'קבלת סיכום מכירות' (Hebrew: 'Get sales summary') indicate data retrieval without modification. The pattern matches query/fetch operations that retrieve analytics data.
Attacks that exploit this kind of access
קבלת סיכום מכירות. It is categorised as a Read tool in the Stevia Store MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stevia Store MCP Server MCP server in PolicyLayer and add a rule for get_sales_summary: 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.
get_sales_summary 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_sales_summary 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_sales_summary. 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_sales_summary 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 →