timecode_frames
Count the frames in an SMPTE timecode from midnight. Rates are 24, 25 and 30. A colon is non-drop and a semicolon is drop-frame, which is only legal at 30. Drop-frame skips 00 and 01 at the start of each minute except every tenth minute, so 01:00:00;00 is frame 107892 rather than 108000. Price: $...
This record as markdown: /tools/com-it-scorptech-x402/timecode-frames.md
What timecode_frames does on ScorpTech x402 API
AI agents call timecode_frames 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 | Yes | |
rate | integer | — |
Parameters from the server's own tool schema.
Why timecode_frames is rated Critical
An AI agent that decides to call timecode_frames 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) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs timecode_frames 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_frames, this is the rule to start with:
timecode_frames 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_frames call is checked against it from then on.
Questions about timecode_frames
Count the frames in an SMPTE timecode from midnight. Rates are 24, 25 and 30. A colon is non-drop and a semicolon is drop-frame, which is only legal at 30. Drop-frame skips 00 and 01 at the start of each minute except every tenth minute, so 01:00:00;00 is frame 107892 rather than 108000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/timecode-frames. 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_frames accepts 2 parameters: code, rate. Required: code. 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_frames: 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_frames 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_frames 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_frames. 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_frames 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