Get details of a specific phone number including its agent bindings. WHEN TO USE: - To check which agents are bound (inbound and outbound) to a specific number - To diagnose why create_phone_call returns 404 (missing outbound agent binding) - To confirm the bound agent_version before overriding c...
AI agents call get_phone_number to retrieve information from Apple Shortcuts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing phone number configuration data without any side effects. It is purely informational and diagnostic in nature. The low severity reflects minimal blast radius—exposing which agents are bound to phone numbers is a configuration detail with no direct operational impact.
From the tool's definition Tool description explicitly states 'Get details of a specific phone number including its agent bindings' and use cases are limited to checking/confirming configuration: 'check which agents are bound', 'diagnose', 'confirm the bound agent_version'.
Documented attack patterns abuse exactly the kind of access get_phone_number gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for get_phone_number:
{
"version": "1",
"default": "deny",
"tools": {
"get_phone_number": {}
}
}get_phone_number is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get details of a specific phone number including its agent bindings. WHEN TO USE: - To check which agents are bound (inbound and outbound) to a specific number - To diagnose why create_phone_call returns 404 (missing outbound agent binding) - To confirm the bound agent_version before overriding call routing COMMON MISTAKES: - Checking only that the number exists; outbound calls require outbound_agents - Missing that the bound agent_version differs from the version you intend to use ERROR RECOVERY: - 401: API key is missing or invalid → configure_retell_api_key - 404: phone number not found → list_phone_numbers and use the exact E.164 value RELATED TOOLS: - list_phone_numbers: Discover available numbers - update_phone_number: Add/fix inbound or outbound bindings - get_agent_versions: Verify bound agent versions - create_phone_call: Use this phone_number as from_number RETURNS: phone_number, nickname, inbound_agents, outbound_agents, phone number config fields. It is categorised as a Read tool in the Apple Shortcuts MCP Server, which means it retrieves data without modifying state.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for get_phone_number: 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 Apple Shortcuts. Nothing to install.
get_phone_number 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_phone_number 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_phone_number. 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_phone_number is provided by the Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.