AI agents call get_service_names to retrieve information from Azure Pricing MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves service names from the Azure pricing API, which is a pure data retrieval operation with no capability to modify, delete, or execute actions. The empty description and naming convention suggest it returns a list of available service names for querying purposes. The severity is low because misuse would only expose pricing metadata without financial impact or system compromise.
From the tool's definition Tool name 'get_service_names' indicates data retrieval. Server description emphasizes 'querying' pricing information with 'no side effects' implied by the read-only nature of the Azure Retail Prices API.
Documented attack patterns abuse exactly the kind of access get_service_names gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure Pricing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_service_names:
{
"version": "1",
"default": "deny",
"tools": {
"get_service_names": {}
}
}get_service_names 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_service_names. It is categorised as a Read tool in the Azure Pricing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure Pricing MCP Server MCP server in PolicyLayer and add a rule for get_service_names: 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 Azure Pricing MCP Server. Nothing to install.
get_service_names 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_service_names 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_service_names. 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_service_names is provided by the Azure Pricing MCP Server MCP server (sboludaf/mcp-azure-pricing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Azure Pricing 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.
4 Azure Pricing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.