AI agents call compare_hashes to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
hash1 | string | Yes | First hash |
hash2 | string | Yes | Second hash |
Parameters from the server's own tool schema.
This tool performs a comparison operation between two hashes, which is a read-only action that returns a boolean or comparison result without creating, modifying, deleting, or executing external operations. The emphasis on 'constant time' (timing-safe comparison) is a security property to prevent timing attacks, not an indicator of a higher-risk category.
From the tool's definition Tool name 'compare_hashes' and description 'Compare two hashes in constant time' indicates a query/comparison operation with no modification or side effects. It retrieves or evaluates data deterministically.
Attacks that exploit this kind of access
Compare two hashes in constant time (timing-safe). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
compare_hashes accepts 2 parameters: hash1, hash2. Required: hash1, hash2. 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 compare_hashes: 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.
compare_hashes 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 compare_hashes 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 compare_hashes. 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.
compare_hashes 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.
compare_hashes is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →