add_visitor
Create a Central NAC visitor account. name=login username; expire_at ISO 8601.
This record as markdown: /tools/secure-ssid-centralmcp/add-visitor.md
What add_visitor does on API-Central
AI agents use add_visitor to create or update resources in API-Central, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.
Why add_visitor is rated Medium
This tool creates new visitor/user accounts in the network access control system, which is a Write operation—data is created and can be modified or deleted. Severity is medium because compromised account creation could enable unauthorized network access, but the blast radius is somewhat contained by the visitor account nature and expiration settings.
From the tool's definition Create a Central NAC visitor account. The tool generates new user accounts with parameters for username (name=login username) and expiration time (expire_at ISO 8601), which are reversible creations of authentication credentials.
Attacks that exploit this kind of access
The rule that runs add_visitor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_visitor, this is the rule to start with:
add_visitor 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.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every add_visitor call is checked against it from then on.
Questions about add_visitor
Create a Central NAC visitor account. name=login username; expire_at ISO 8601. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API-Central MCP server in PolicyLayer and add a rule for add_visitor: 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 API-Central. Nothing to install.
add_visitor 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 add_visitor 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 add_visitor. 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.
add_visitor is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue