Convert a datetime between IANA timezones.
AI agents use convert_time to create or update resources in MCP Server Fly — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server Fly environment.
An AI agent can call convert_time faster than any human can review — one bad instruction and it creates or modifies resources in MCP Server Fly by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Convert a datetime between IANA timezones. It is categorised as a Write tool in the MCP Server Fly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server Fly MCP server in PolicyLayer and add a rule for convert_time: 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 MCP Server Fly. Nothing to install.
convert_time is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the convert_time 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 convert_time. 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.
convert_time is provided by the MCP Server Fly MCP server (kushalkachari993-dev/mcp-server-fly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
convert_time is one line of MCP Server Fly'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 →