custom_name
A other tool on the Reservation Platform MCP server.
This record as markdown: /tools/pak3430-reservation-platform-mcp-server/custom-name.md
What custom_name does on Reservation Platform MCP Server
AI agents call custom_name as a supporting operation in Reservation Platform MCP Server workflows.
Why custom_name is rated Low
With no description and an ambiguous name 'custom_name', there is insufficient information to classify this tool into any meaningful risk category. The name alone does not suggest any specific action. Confidence is very low due to the lack of evidence.
From the tool's definition Tool name is 'custom_name' with an empty description, providing no information about what the tool does.
Attacks that exploit this kind of access
The rule that runs custom_name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Reservation Platform MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For custom_name, this is the rule to start with:
custom_name gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Reservation Platform MCP Server, apply this rule, and every custom_name call is checked against it from then on.
Questions about custom_name
custom_name is a other tool on the Reservation Platform MCP Server MCP server. It is categorised as a Other tool in the Reservation Platform MCP Server MCP Server, which means it performs auxiliary operations.
Register the Reservation Platform MCP Server MCP server in PolicyLayer and add a rule for custom_name: 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 Reservation Platform MCP Server. Nothing to install.
custom_name is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the custom_name 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 custom_name. 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.
custom_name is provided by the Reservation Platform MCP Server MCP server (pak3430/reservation-platform-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Reservation Platform MCP Server, and thousands of servers like it.
This server
Across the catalogue