get_temperature_checks
Get temperature check polls
This record as markdown: /tools/indigoprotocol-indigo-mcp/get-temperature-checks.md
What get_temperature_checks does on Indigo Protocol MCP
AI agents call get_temperature_checks to retrieve information from Indigo Protocol MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_temperature_checks is rated Low
This tool retrieves polling or sentiment data from the Indigo Protocol without modifying, executing, or destructing anything. It is a straightforward data query with no capacity to change state or trigger irreversible actions. Low severity because misuse would only expose information, not affect protocol state or finances.
From the tool's definition Tool name 'get_temperature_checks' and description 'Get temperature check polls' indicate a retrieval operation with no side effects. The verb 'get' combined with the read-only nature of polls (which are data queries) confirms this is a read operation.
Attacks that exploit this kind of access
The rule that runs get_temperature_checks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Indigo Protocol MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_temperature_checks, this is the rule to start with:
get_temperature_checks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Indigo Protocol MCP, apply this rule, and every get_temperature_checks call is checked against it from then on.
Questions about get_temperature_checks
Get temperature check polls. It is categorised as a Read tool in the Indigo Protocol MCP MCP Server, which means it retrieves data without modifying state.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for get_temperature_checks: 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 Indigo Protocol MCP. Nothing to install.
get_temperature_checks 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_temperature_checks 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_temperature_checks. 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_temperature_checks is provided by the Indigo Protocol MCP server (indigoprotocol/indigo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Indigo Protocol, and thousands of servers like it.
This server
Across the catalogue