This record as markdown: /tools/io-tinyfn-tinyfn/user-agent.md
What user_agent does on TinyFn
AI agents call user_agent 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 |
|---|---|---|---|
ua | string | Yes | User agent string to parse |
Parameters from the server's own tool schema.
Why user_agent is rated Low
This tool performs string parsing and analysis only—a deterministic read operation that extracts information from user agent headers without side effects. No data is modified, code is executed, or external systems are invoked. It fits the 'Read' category as a retrieval/query operation with minimal security risk.
From the tool's definition Tool name 'user_agent' and description 'Parse a user agent string' indicate it retrieves and analyzes existing data without modification, creation, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs user_agent 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 user_agent, this is the rule to start with:
user_agent 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 user_agent call is checked against it from then on.
Questions about user_agent
Parse a user agent string. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
user_agent accepts 1 parameter: ua. Required: ua. 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 user_agent: 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.
user_agent 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 user_agent 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 user_agent. 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.
user_agent 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