Get or update Pancake POS shop information. Actions: get (retrieve shop profile), update (update shop details).
AI agents use get_shop_info to create or update resources in Pancake POS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pancake POS MCP environment.
The tool supports both read and write operations. Since it includes an 'update' action that modifies shop details, it must be classified at the higher severity level. Applying the most-severe-applicable rule, this is a Write tool. Misuse could alter shop profile information (name, address, settings), which could disrupt business operations but is likely reversible.
From the tool's definition Actions: get (retrieve shop profile), update (update shop details)
Attacks that exploit this kind of access
Get or update Pancake POS shop information. Actions: get (retrieve shop profile), update (update shop details). It is categorised as a Write tool in the Pancake POS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pancake POS MCP server in PolicyLayer and add a rule for get_shop_info: 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 Pancake POS MCP. Nothing to install.
get_shop_info 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 get_shop_info 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_shop_info. 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_shop_info is provided by the Pancake POS MCP server (svn4pro/pancake-pos-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 →