New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mist_get_site_sle_metric_summary

A read tool on the API-Central MCP server.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/mist-get-site-sle-metric-summary.md

What mist_get_site_sle_metric_summary does on API-Central

AI agents call mist_get_site_sle_metric_summary to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why mist_get_site_sle_metric_summary is rated Low

The tool appears to retrieve or query SLE (Service Level Expectation) metrics for a site, which is a read-only monitoring operation with no side effects. The description is empty, but the name structure and context within a network operations platform strongly indicate this is a data retrieval tool.

From the tool's definition Tool name 'mist_get_site_sle_metric_summary' uses the pattern 'get_*' which indicates data retrieval. The 'mist_' prefix suggests integration with Mist (a network monitoring platform).

Questions about mist_get_site_sle_metric_summary

What does the mist_get_site_sle_metric_summary tool do? +

mist_get_site_sle_metric_summary is a read tool on the API-Central MCP server. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mist_get_site_sle_metric_summary? +

Register the API-Central MCP server in PolicyLayer and add a rule for mist_get_site_sle_metric_summary: 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.

What risk level is mist_get_site_sle_metric_summary? +

mist_get_site_sle_metric_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mist_get_site_sle_metric_summary? +

Yes. Add a rate_limit block to the mist_get_site_sle_metric_summary 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.

How do I block mist_get_site_sle_metric_summary completely? +

Set action: deny in the PolicyLayer policy for mist_get_site_sle_metric_summary. 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.

What MCP server provides mist_get_site_sle_metric_summary? +

mist_get_site_sle_metric_summary 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of API-Central's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.