Get the monthly horoscope for a zodiac sign. Returns the prediction text for the current month plus challenging and standout days.
AI agents call monthly_horoscope to retrieve information from Mcp Horoscope without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sign | string | Yes | Zodiac sign (case-insensitive). One of: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces. |
Parameters from the server's own tool schema.
This tool retrieves horoscope predictions from an API and returns them to the caller. It performs a read-only query operation with no capability to modify state, execute arbitrary code, delete data, or commit financial transactions. The blast radius of misuse is minimal—an agent could only retrieve unwanted horoscope data, which has no security, financial, or operational impact.
From the tool's definition Tool name is 'monthly_horoscope' and description states it 'Get[s] the monthly horoscope for a zodiac sign' and 'Returns the prediction text'. These verbs (get, return) indicate pure data retrieval with no modification, creation, deletion, or side effects.
Attacks that exploit this kind of access
Get the monthly horoscope for a zodiac sign. Returns the prediction text for the current month plus challenging and standout days. It is categorised as a Read tool in the Mcp Horoscope MCP Server, which means it retrieves data without modifying state.
monthly_horoscope accepts 1 parameter: sign. Required: sign. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Horoscope MCP server in PolicyLayer and add a rule for monthly_horoscope: 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 Mcp Horoscope. Nothing to install.
monthly_horoscope 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 monthly_horoscope 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 monthly_horoscope. 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.
monthly_horoscope is provided by the Mcp Horoscope MCP server (https://gateway.pipeworx.io/horoscope/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 →