AI agents invoke nina_move_focuser 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.
Based on the server context and tool name, this tool likely commands a physical focuser device to move, which is an external hardware operation. Moving a focuser is a physical actuator command (Execute category) rather than purely reading data or writing config. It could cause minor issues if misused (e.g., moving focuser to wrong position), hence medium severity. Low confidence due to empty description.
From the tool's definition Tool name 'nina_move_focuser' on a server that controls astrophotography equipment including focusers. Description is empty.
Documented attack patterns abuse exactly the kind of access nina_move_focuser 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_move_focuser:
{
"version": "1",
"default": "deny",
"tools": {
"nina_move_focuser": {
"limits": [
{
"counter": "nina_move_focuser_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}nina_move_focuser 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.
nina_move_focuser. 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_move_focuser: 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_move_focuser 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_move_focuser 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_move_focuser. 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_move_focuser 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.