get_body_temperature

Get body temperature data from Elixir biosensing. Available on compatible Polar devices with temperature sensing capabilities.

Server Polar MCP Server nelsonnew/polar-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_body_temperature does on Polar MCP Server

AI agents call get_body_temperature to retrieve information from Polar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_body_temperature needs a policy

This tool retrieves body temperature sensor data from a Polar device without any side effects, modifications, or irreversible actions. It is a straightforward read operation on health/fitness data. Severity is low because unauthorized access to personal biometric data has limited immediate blast radius, though it could raise privacy concerns in some contexts.

From the tool's definition Tool name 'get_body_temperature' and description 'Get body temperature data' indicate data retrieval only. No modification, deletion, execution, or financial operations are described.

Questions about get_body_temperature

What does the get_body_temperature tool do? +

Get body temperature data from Elixir biosensing. Available on compatible Polar devices with temperature sensing capabilities. It is categorised as a Read tool in the Polar MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_body_temperature? +

Register the Polar MCP Server MCP server in PolicyLayer and add a rule for get_body_temperature: 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 Polar MCP Server. Nothing to install.

What risk level is get_body_temperature? +

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

Can I rate-limit get_body_temperature? +

Yes. Add a rate_limit block to the get_body_temperature 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 get_body_temperature completely? +

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

get_body_temperature is provided by the Polar MCP Server MCP server (nelsonnew/polar-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.