Get count of advisories affecting infrastructure by severity
AI agents call get_tam_advisory_count to retrieve information from Intersight MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve advisory count metrics. It has no side effects, does not execute operations, does not modify infrastructure state, and does not commit financial transactions. The verb 'get' and noun 'count' confirm a data retrieval operation.
From the tool's definition Tool name 'get_tam_advisory_count' and description 'Get count of advisories affecting infrastructure by severity' indicate a retrieval operation that queries advisory counts without modifying, executing, or deleting any data.
Documented attack patterns abuse exactly the kind of access get_tam_advisory_count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intersight MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tam_advisory_count:
{
"version": "1",
"default": "deny",
"tools": {
"get_tam_advisory_count": {}
}
}get_tam_advisory_count 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.
Get count of advisories affecting infrastructure by severity. It is categorised as a Read tool in the Intersight MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intersight MCP Server MCP server in PolicyLayer and add a rule for get_tam_advisory_count: 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 Intersight MCP Server. Nothing to install.
get_tam_advisory_count 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_tam_advisory_count 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_tam_advisory_count. 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_tam_advisory_count is provided by the Intersight MCP Server MCP server (jim-coyne/intersight_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intersight MCP Server, 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.
198 Intersight MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.