shelly_get_status

// WHEN AI AGENTS USE THIS TOOL

AI agents call shelly_get_status to retrieve information from Shelly without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON SHELLY_GET_STATUS

Even though shelly_get_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

shelly.yaml

tools:
  shelly_get_status:
    rules:
      - action: allow

See the full Shelly policy for all 9 tools.

// DETAILS

Tool Name shelly_get_status

Category Read

MCP Server Shelly MCP Server

Risk Level Low

// MORE SHELLY TOOLS

Write shelly_cover_control Write shelly_discover_and_save_devices Write shelly_discover_save_and_validate Write shelly_rpc_call Write shelly_switch_set Write shelly_update_device_credentials Read shelly_get_device_info Read shelly_list_devices

View all 9 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like shelly_get_status have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Firecrawl Web Scraping Server firecrawl_check_crawl_status Firecrawl Web Scraping Server firecrawl_crawl Firecrawl Web Scraping Server firecrawl_deep_research Firecrawl Web Scraping Server firecrawl_extract Firecrawl Web Scraping Server firecrawl_map Firecrawl Web Scraping Server firecrawl_scrape

// RELATED READING

// FAQ

What does the shelly_get_status tool do? +

Get full status for a Shelly device using Shelly.GetStatus.. It is categorised as a Read tool in the Shelly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on shelly_get_status? +

Add a rule in your Intercept YAML policy under the tools section for shelly_get_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Shelly MCP server.

What risk level is shelly_get_status? +

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

Can I rate-limit shelly_get_status? +

Yes. Add a rate_limit block to the shelly_get_status rule in your Intercept 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 shelly_get_status completely? +

Set action: deny in the Intercept policy for shelly_get_status. 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 shelly_get_status? +

shelly_get_status is provided by the Shelly MCP server (shelly-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.