This record as markdown: /tools/io-tinyfn-tinyfn/verify-hash.md
What verify_hash does on TinyFn
AI agents call verify_hash 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 |
|---|---|---|---|
text | string | Yes | Original text |
algorithm | string | — | Algorithm used |
hash_value | string | Yes | Hash to verify |
Parameters from the server's own tool schema.
Why verify_hash is rated Low
This tool retrieves or compares data without creating, modifying, or deleting anything. It performs a cryptographic validation check (hash comparison), which is deterministic and read-only. No data is written, executed, destroyed, or financially affected. This is a classic Read category tool.
From the tool's definition Tool name 'verify_hash' and description 'Verify a hash matches the text' indicate a comparison/validation operation with no side effects. The verb 'verify' is a read-only operation that checks equality between a hash and input text.
Attacks that exploit this kind of access
The rule that runs verify_hash 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 verify_hash, this is the rule to start with:
verify_hash 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 verify_hash call is checked against it from then on.
Questions about verify_hash
Verify a hash matches the text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
verify_hash accepts 3 parameters: text, algorithm, hash_value. Required: text, hash_value. 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 verify_hash: 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.
verify_hash 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 verify_hash 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 verify_hash. 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.
verify_hash 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