Retrieves the list of contacts to inform for an object
AI agents call get_contacts_for_object to retrieve information from Nagios without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Nagios configuration data to return contact information associated with monitoring objects. It performs no modifications, deletions, or external operations. The contact list is reference data used for alert routing, not sensitive enough to warrant higher severity when read via a monitoring API.
From the tool's definition Tool name and description indicate retrieval only: 'Retrieves the list of contacts' — a query operation with no side effects. Consistent with sibling tools on this server (get_alerts, get_comments, get_host_status, etc.) which are all read-only queries.
Documented attack patterns abuse exactly the kind of access get_contacts_for_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nagios, and nothing reaches the server without passing your rules. This is the rule we recommend for get_contacts_for_object:
{
"version": "1",
"default": "deny",
"tools": {
"get_contacts_for_object": {}
}
}get_contacts_for_object is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves the list of contacts to inform for an object. It is categorised as a Read tool in the Nagios MCP Server, which means it retrieves data without modifying state.
Register the Nagios MCP server in PolicyLayer and add a rule for get_contacts_for_object: 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 Nagios. Nothing to install.
get_contacts_for_object is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_contacts_for_object 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 get_contacts_for_object. 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.
get_contacts_for_object is provided by the Nagios MCP server (prospire-technology-services/nagios-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nagios, 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.
17 Nagios tools catalogued and risk-classified — across an index of 43,000+ MCP servers.