Securely store API credentials for Resy or OpenTable.
AI agents use set_credentials to create or update resources in Restaurant Reservation MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Restaurant Reservation MCP Server environment.
The tool creates or modifies authentication credentials in a data store. While credentials themselves are sensitive, this operation is reversible (credentials can be updated or removed), making it Write rather than Destructive.
From the tool's definition Tool name is 'set_credentials' and description states it 'Securely store API credentials for Resy or OpenTable.' This modifies stored authentication data.
Attacks that exploit this kind of access
Securely store API credentials for Resy or OpenTable. It is categorised as a Write tool in the Restaurant Reservation MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Restaurant Reservation MCP Server MCP server in PolicyLayer and add a rule for set_credentials: 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 Reservation MCP Server. Nothing to install.
set_credentials 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 set_credentials 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 set_credentials. 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.
set_credentials is provided by the Restaurant Reservation MCP Server MCP server (jrklein343-svg/restaurant-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 →