This record as markdown: /tools/io-tinyfn-tinyfn/validate-phone.md
What validate_phone does on TinyFn
AI agents call validate_phone to retrieve information from TinyFn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
phone | string | Yes | Phone number to validate |
country | string | — | Country code for validation |
Parameters from the server's own tool schema.
Why validate_phone is rated Low
This tool performs input validation—a common deterministic utility that retrieves no data, modifies nothing, and triggers no side effects or external operations. It is purely informational, making it a Read operation with minimal security risk. Severity is low because misuse would only return incorrect validation results, not enable harmful downstream actions.
From the tool's definition Tool name is 'validate_phone' and description states 'Validate a phone number.' Validation is a read-only operation that checks input against a pattern or ruleset and returns a boolean or validation result without modifying, executing, or affecting any…
Attacks that exploit this kind of access
The rule that runs validate_phone safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate_phone, this is the rule to start with:
validate_phone is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every validate_phone call is checked against it from then on.
Questions about validate_phone
Validate a phone number. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
validate_phone accepts 2 parameters: phone, country. Required: phone. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for validate_phone: 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 TinyFn. Nothing to install.
validate_phone 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 validate_phone 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 validate_phone. 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.
validate_phone is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue