camera_recordings_day
List the recorded pieces of one day on a camera's memory card: start, end, length and whether each was
This record as markdown: /tools/tolpo/camera-recordings-day.md
What camera_recordings_day does on Tolpo
AI agents invoke camera_recordings_day to trigger actions in Tolpo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why camera_recordings_day is rated High
camera_recordings_day triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs camera_recordings_day safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tolpo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For camera_recordings_day, this is the rule to start with:
camera_recordings_day stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tolpo, apply this rule, and every camera_recordings_day call is checked against it from then on.
Questions about camera_recordings_day
List the recorded pieces of one day on a camera's memory card: start, end, length and whether each was. It is categorised as a Execute tool in the Tolpo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tolpo MCP server in PolicyLayer and add a rule for camera_recordings_day: 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 Tolpo. Nothing to install.
camera_recordings_day is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the camera_recordings_day 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 camera_recordings_day. 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.
camera_recordings_day is provided by the Tolpo MCP server (signerless/tolpo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tolpo, and thousands of servers like it.
Across the catalogue