get_promo_details
AI agents call get_promo_details to retrieve information from Restaurant Backend MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or query promotional details without modifying data or triggering external effects. The 'get_' prefix is typical of read operations. No side effects are indicated. However, confidence is moderately reduced due to the empty description, which could theoretically conceal a more complex operation, though sibling context (apply_promo_code for modifications) supports the read classification.
From the tool's definition Tool name 'get_promo_details' indicates retrieval of promotional information. Empty description provides limited direct evidence, but the sibling tool 'apply_promo_code' suggests this is part of a promo management system where 'get_promo_details' queries…
Attacks that exploit this kind of access
get_promo_details. It is categorised as a Read tool in the Restaurant Backend MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Restaurant Backend MCP Server MCP server in PolicyLayer and add a rule for get_promo_details: 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 Restaurant Backend MCP Server. Nothing to install.
get_promo_details 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_promo_details 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_promo_details. 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_promo_details is provided by the Restaurant Backend MCP Server MCP server (pasanis/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 →