Get store information (about, contact, terms, etc.)
AI agents call get_store_info to retrieve information from Arham Jewellers MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves publicly available store information such as about, contact details, and terms. It performs a read-only query with no capability to modify, delete, or execute operations. The information retrieved is typically non-sensitive business metadata. Severity is low due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_store_info' and description states 'Get store information (about, contact, terms, etc.)', indicating retrieval of static store metadata with no side effects.
Attacks that exploit this kind of access
Get store information (about, contact, terms, etc.). It is categorised as a Read tool in the Arham Jewellers MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Arham Jewellers MCP Server MCP server in PolicyLayer and add a rule for get_store_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 Arham Jewellers MCP Server. Nothing to install.
get_store_info 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_store_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_store_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_store_info is provided by the Arham Jewellers MCP Server MCP server (parthhimself0/arham-mcp-server). 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 →