updown_tf_duration
Round duration in seconds for a timeframe.
This record as markdown: /tools/launch-on-basis-mcp-ts/updown-tf-duration.md
What updown_tf_duration does on Basis MCP Server
AI agents call updown_tf_duration to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why updown_tf_duration is rated Low
The tool appears to return a computed or queried duration value (in seconds) for a given timeframe. This is a read/query operation with no financial, destructive, or write implications. Confidence is moderate because the description is minimal and the broader server context involves financial operations, but the tool itself seems purely informational.
From the tool's definition 'Round duration in seconds for a timeframe' — retrieves/computes a duration value, no side effects implied
Attacks that exploit this kind of access
The rule that runs updown_tf_duration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updown_tf_duration, this is the rule to start with:
updown_tf_duration 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 Basis MCP Server, apply this rule, and every updown_tf_duration call is checked against it from then on.
Questions about updown_tf_duration
Round duration in seconds for a timeframe. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for updown_tf_duration: 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 Basis MCP Server. Nothing to install.
updown_tf_duration 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 updown_tf_duration 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 updown_tf_duration. 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.
updown_tf_duration is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue