AI agents use nina_connect_dome to create or update resources in Nina Advanced API MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nina Advanced API MCP environment.
Based on the naming pattern of sibling tools (nina_connect, nina_connect_camera, nina_connect_filterwheel, nina_connect_flatpanel), this tool likely establishes a connection to a dome controller device. Connection operations are Write-category as they create a new connection state. Severity is medium because connecting to dome control could enable subsequent dome operations.
From the tool's definition Tool name 'nina_connect_dome' on a server that controls astrophotography equipment including domes. Description is empty.
Documented attack patterns abuse exactly the kind of access nina_connect_dome 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_connect_dome:
{
"version": "1",
"default": "deny",
"tools": {
"nina_connect_dome": {
"limits": [
{
"counter": "nina_connect_dome_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}nina_connect_dome stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
nina_connect_dome. It is categorised as a Write tool in the Nina Advanced API MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nina Advanced API MCP server in PolicyLayer and add a rule for nina_connect_dome: 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_connect_dome is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the nina_connect_dome 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_connect_dome. 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_connect_dome 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.