AI agents invoke nina_wait to trigger actions in Nina Advanced API MCP. 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.
The tool executes a command that causes the astrophotography system to pause for a caller-specified duration. While the operation itself is harmless (a time delay), it is still an Execute action because it triggers external behavior in the control system. It does not retrieve data (Read), modify persistent state (Write), delete anything (Destructive), or move money (Financial).
From the tool's definition Tool name is 'nina_wait' with description 'Wait for a specified duration in seconds.' This triggers an external operation (a timed delay/pause) whose effects depend on the argument (duration value).
Documented attack patterns abuse exactly the kind of access nina_wait gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nina Advanced API MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for nina_wait:
{
"version": "1",
"default": "deny",
"tools": {
"nina_wait": {
"limits": [
{
"counter": "nina_wait_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}nina_wait 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.
Free to start. No card required.
Wait for a specified duration in seconds. It is categorised as a Execute tool in the Nina Advanced API MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nina Advanced API MCP server in PolicyLayer and add a rule for nina_wait: 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 Nina Advanced API MCP. Nothing to install.
nina_wait 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 nina_wait 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 nina_wait. 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.
nina_wait is provided by the Nina Advanced API MCP server (padev1/nina_advanced_api_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nina Advanced API MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
103 Nina Advanced API MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.