constant_time_compare
Compare two strings in constant time (timing-safe).
This record as markdown: /tools/io-tinyfn-tinyfn/constant-time-compare.md
What constant_time_compare does on TinyFn
AI agents call constant_time_compare 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 |
|---|---|---|---|
a | string | Yes | First string |
b | string | Yes | Second string |
Parameters from the server's own tool schema.
Why constant_time_compare is rated Low
This is a deterministic cryptographic utility for timing-safe string comparison (commonly used to prevent timing attacks on secrets). It performs a read-only comparison operation with no state changes, data creation, deletion, or external side effects. The blast radius of misuse is minimal — worst case an agent compares strings it shouldn't, but no data is harmed.
From the tool's definition Tool description states it 'Compare[s] two strings in constant time' — a comparison operation that retrieves or evaluates data with no side effects. Returns a boolean result without modifying, creating, or deleting any data.
Attacks that exploit this kind of access
The rule that runs constant_time_compare 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 constant_time_compare, this is the rule to start with:
constant_time_compare 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 constant_time_compare call is checked against it from then on.
Questions about constant_time_compare
Compare two strings 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.
constant_time_compare accepts 2 parameters: a, b. Required: a, b. 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 constant_time_compare: 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.
constant_time_compare 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 constant_time_compare 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 constant_time_compare. 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.
constant_time_compare 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