Send the mount to its home position in NINA astronomy software.
AI agents invoke nina_home_mount 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.
This tool triggers a physical hardware action — moving the telescope mount to its home position. It executes an external operation on physical equipment. While it is a controlled movement (homing is a standard, recoverable operation), it still commands real-world hardware motion.
From the tool's definition Send the mount to its home position in NINA astronomy software
Documented attack patterns abuse exactly the kind of access nina_home_mount 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_home_mount:
{
"version": "1",
"default": "deny",
"tools": {
"nina_home_mount": {
"limits": [
{
"counter": "nina_home_mount_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}nina_home_mount 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.
Send the mount to its home position in NINA astronomy software. 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_home_mount: 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_home_mount 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_home_mount 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_home_mount. 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_home_mount 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.