Return plan limits for the current API key (GET /v1/limits).
AI agents call get_limits to retrieve information from Sentinel Signal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves plan limits associated with an API key. It performs information retrieval only (GET endpoint) with no capability to modify, delete, or execute operations. The severity is low because disclosure of plan limits poses minimal risk—it is informational metadata that does not directly impact healthcare claims processing, patient data, or financial transactions.
From the tool's definition Tool description explicitly states 'Return plan limits' and uses GET method, indicating a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
Return plan limits for the current API key (GET /v1/limits). It is categorised as a Read tool in the Sentinel Signal MCP MCP Server, which means it retrieves data without modifying state.
Register the Sentinel Signal MCP server in PolicyLayer and add a rule for get_limits: 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 Sentinel Signal MCP. Nothing to install.
get_limits 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_limits 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_limits. 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_limits is provided by the Sentinel Signal MCP server (sentinelsignal/sentinel-signal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →