get_appointment

Get detailed information about a single appointment by its ID.

SERVERShopmonkey MCP Server SOURCEabbottdevelopments/shopmonkey-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abbottdevelopments-shopmonkey-mcp-server/get-appointment.md

WHAT IT DOES

What get_appointment does on Shopmonkey MCP Server

AI agents call get_appointment to retrieve information from Shopmonkey MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_appointment is rated Low

The tool retrieves appointment data without modifying, deleting, or executing any operations. This is a straightforward read operation typical of GET endpoints in REST APIs. The blast radius of misuse is minimal—an AI agent could only view existing appointment information, posing no risk to data integrity or financial operations.

From the tool's definition Tool name 'get_appointment' and description 'Get detailed information about a single appointment by its ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_appointment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Shopmonkey MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_appointment, this is the rule to start with:

get_appointment Allowed

get_appointment is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_appointment": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Shopmonkey MCP Server, apply this rule, and every get_appointment call is checked against it from then on.

FAQ

Questions about get_appointment

What does the get_appointment tool do? +

Get detailed information about a single appointment by its ID. It is categorised as a Read tool in the Shopmonkey MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_appointment? +

Register the Shopmonkey MCP Server MCP server in PolicyLayer and add a rule for get_appointment: 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 Shopmonkey MCP Server. Nothing to install.

What risk level is get_appointment? +

get_appointment is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_appointment? +

Yes. Add a rate_limit block to the get_appointment 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.

How do I block get_appointment completely? +

Set action: deny in the PolicyLayer policy for get_appointment. 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.

What MCP server provides get_appointment? +

get_appointment is provided by the Shopmonkey MCP Server MCP server (abbottdevelopments/shopmonkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Shopmonkey MCP Server, and thousands of servers like it.

This server

All 64 Shopmonkey MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →