timecode_add
Add a signed frame count to a timecode and stay inside the same day. A result before midnight or at the next midnight is rejected. The semicolon, if present, keeps the result in drop-frame. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/a...
This record as markdown: /tools/com-it-scorptech-x402/timecode-add.md
What timecode_add does on ScorpTech x402 API
AI agents use timecode_add to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
add | integer | Yes | |
code | string | Yes | |
rate | integer | — |
Parameters from the server's own tool schema.
Why timecode_add is rated Medium
An AI agent can call timecode_add faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs timecode_add 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_add, this is the rule to start with:
timecode_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every timecode_add call is checked against it from then on.
Questions about timecode_add
Add a signed frame count to a timecode and stay inside the same day. A result before midnight or at the next midnight is rejected. The semicolon, if present, keeps the result in drop-frame. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/timecode-add. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
timecode_add accepts 3 parameters: add, code, rate. Required: add, 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_add: 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_add 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 timecode_add 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_add. 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_add 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.
This server
Across the catalogue