get_glucose_history

Retrieve historical glucose readings for analysis. Returns an array of timestamped glucose values. Useful for reviewing past glucose levels, identifying patterns, or checking overnight values. Default retrieves 24 hours of data.

Server LibreLink MCP Server sedoglia/librelink-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_glucose_history does on LibreLink MCP Server

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

Why get_glucose_history needs a policy

This tool queries and retrieves historical glucose data from a LibreLink account without modifying, deleting, or executing anything. It is a straightforward read operation with no side effects. Severity is low because glucose data is personal health information, but retrieval alone poses minimal risk—the concern would be authentication/authorization rather than the tool's inherent capability.

From the tool's definition Tool name 'get_glucose_history' and description 'Retrieve historical glucose readings' indicate data retrieval with 'Returns an array of timestamped glucose values.' No modification, deletion, execution, or financial operations are described.

Questions about get_glucose_history

What does the get_glucose_history tool do? +

Retrieve historical glucose readings for analysis. Returns an array of timestamped glucose values. Useful for reviewing past glucose levels, identifying patterns, or checking overnight values. Default retrieves 24 hours of data. It is categorised as a Read tool in the LibreLink MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_glucose_history? +

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

What risk level is get_glucose_history? +

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

Can I rate-limit get_glucose_history? +

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

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

get_glucose_history is provided by the LibreLink MCP Server MCP server (sedoglia/librelink-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.