create_review
AI agents use create_review to create or update resources in Restaurant Backend MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Restaurant Backend MCP Server environment.
The tool creates new review data, which is a reversible write operation. Severity is medium because an AI agent could create false or misleading reviews that could damage restaurant reputation or manipulate customer perception, though the damage can be addressed by deletion.
From the tool's definition Tool name 'create_review' indicates creation of new data. Description is empty but naming convention and context as part of restaurant backend management system suggests the tool creates customer review records.
Attacks that exploit this kind of access
create_review. It is categorised as a Write tool in the Restaurant Backend MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Restaurant Backend MCP Server MCP server in PolicyLayer and add a rule for create_review: 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.
create_review 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 create_review 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 create_review. 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.
create_review 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 →