get_current_positions
AI agents call get_current_positions to retrieve information from Kerykeion MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves current planetary or celestial positions—a read-only query operation with no side effects, no code execution, and no data modification. No external operations are triggered based on the argument. The empty description lowers confidence slightly, but the name and server context clearly indicate a data-fetching utility.
From the tool's definition Tool name 'get_current_positions' indicates data retrieval of celestial positions. The description is empty, but context from sibling tools (all chart generation functions) and server purpose (astrological calculations) suggests this fetches or queries…
Attacks that exploit this kind of access
get_current_positions. It is categorised as a Read tool in the Kerykeion MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kerykeion MCP Server MCP server in PolicyLayer and add a rule for get_current_positions: 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 Kerykeion MCP Server. Nothing to install.
get_current_positions 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_current_positions 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_current_positions. 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_current_positions is provided by the Kerykeion MCP Server MCP server (jasperb3/kerykeion-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 →