Skip backward in the video by a specified number of seconds.
AI agents invoke seek_backward to trigger actions in MCP Media Server. 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.
This tool executes a media player control operation (seek_backward) that modifies playback state in real time. While the effect is reversible and limited to a local media player, it qualifies as Execute because it triggers an external operation (media player command) with argument-dependent outcomes.
From the tool's definition The tool 'seek_backward' performs an action that 'Skip[s] backward in the video by a specified number of seconds,' which is a command that triggers external operation (media player control) whose effects depend on arguments (number of seconds).
Attacks that exploit this kind of access
Skip backward in the video by a specified number of seconds. It is categorised as a Execute tool in the MCP Media Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Media Server MCP server in PolicyLayer and add a rule for seek_backward: 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 MCP Media Server. Nothing to install.
seek_backward 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 seek_backward 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 seek_backward. 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.
seek_backward is provided by the MCP Media Server MCP server (neal3000/mcp_media_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →