Get e-shop configuration and settings
AI agents call get_shop_config to retrieve information from Upgates 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 configuration data from the e-shop without creating, modifying, deleting, or executing any side effects. Configuration settings are typically non-sensitive operational parameters (e.g., store name, currency, tax settings), and read-only access poses minimal risk if misused by an AI agent. Classified as Read/low severity.
From the tool's definition Tool name 'get_shop_config' with description 'Get e-shop configuration and settings' indicates data retrieval with no modification. The verb 'get' is explicitly a read operation per the category definitions.
Attacks that exploit this kind of access
Get e-shop configuration and settings. It is categorised as a Read tool in the Upgates MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Upgates MCP Server MCP server in PolicyLayer and add a rule for get_shop_config: 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 Upgates MCP Server. Nothing to install.
get_shop_config 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_shop_config 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_config. 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_config is provided by the Upgates MCP Server MCP server (mcp-open/upgates-com-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 →