timecode_duration
Exact length of a frame count. 24, 25 and non-drop 30 use 1/rate second per frame. Drop-frame 30 uses the NTSC frame, 1001/30000 second. Pass a timecode or a frame count, not both. The semicolon selects drop-frame when you pass a code. Price: $0.001 USDC per successful call (x402, Solana). Same t...
This record as markdown: /tools/com-it-scorptech-x402/timecode-duration.md
What timecode_duration does on ScorpTech x402 API
AI agents call timecode_duration to permanently remove resources in ScorpTech x402 API, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | — | |
drop | boolean | — | |
rate | integer | — | |
frames | integer | — |
Parameters from the server's own tool schema.
Why timecode_duration is rated Critical
An AI agent that decides to call timecode_duration doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from ScorpTech x402 API is gone. There is no undo for destructive operations.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs timecode_duration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For timecode_duration, this is the rule to start with:
timecode_duration is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every timecode_duration call is checked against it from then on.
Questions about timecode_duration
Exact length of a frame count. 24, 25 and non-drop 30 use 1/rate second per frame. Drop-frame 30 uses the NTSC frame, 1001/30000 second. Pass a timecode or a frame count, not both. The semicolon selects drop-frame when you pass a code. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/timecode-duration. It is categorised as a Destructive tool in the ScorpTech x402 API MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
timecode_duration accepts 4 parameters: code, drop, rate, frames. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for timecode_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 ScorpTech x402 API. Nothing to install.
timecode_duration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the timecode_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 timecode_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.
timecode_duration is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
Across the catalogue