AI agents call get_keys 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 |
|---|---|---|---|
json_string | string | Yes | JSON object string |
Parameters from the server's own tool schema.
This tool performs a simple read operation on JSON data structures, extracting keys without altering the input. It has no side effects, cannot cause data loss, cannot execute code, and cannot affect system state. Even if misused by an AI agent, the worst outcome is retrieving information already accessible. This is a safe utility function typical of data inspection tools.
From the tool's definition Tool description states 'Get all keys from a JSON object' - a retrieval operation with no modification, deletion, or execution side effects.
Attacks that exploit this kind of access
Get all keys from a JSON object. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
get_keys accepts 1 parameter: json_string. Required: json_string. 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 get_keys: 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.
get_keys 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_keys 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_keys. 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_keys 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.
get_keys 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 →