get_synastry_aspects
AI agents call get_synastry_aspects 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.
Synastry aspects are read-only calculations of planetary relationships between two birth charts. The 'get_' prefix indicates data retrieval with no side effects. Even though the description is empty, the naming convention and functional context within an astrological chart library strongly suggest this is a query operation that returns computed data without creating, executing code, or modifying state.
From the tool's definition Tool name 'get_synastry_aspects' combined with server context indicating it retrieves astrological chart data.
Attacks that exploit this kind of access
get_synastry_aspects. 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_synastry_aspects: 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_synastry_aspects 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_synastry_aspects 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_synastry_aspects. 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_synastry_aspects 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 →