get_sector_rotation
Cross-sectional rotation metrics across core (32 coins) or all-universe cohort. $0.10
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-sector-rotation.md
What get_sector_rotation does on Crypto Intelligence
AI agents call get_sector_rotation to retrieve information from Crypto Intelligence without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_sector_rotation is rated Low
This tool retrieves and queries analytics metrics (sector rotation data) with no side effects, no code execution, and no data modification or deletion. It falls squarely into the Read category. The micropayment is a service fee, not a financial operation that commits obligations or moves trading capital.
From the tool's definition Tool name 'get_sector_rotation' and description 'Cross-sectional rotation metrics across core (32 coins) or all-universe cohort' indicate data retrieval only. The $0.10 cost is a micropayment for query access, not a financial transaction moving user funds.
Attacks that exploit this kind of access
The rule that runs get_sector_rotation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crypto Intelligence, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_sector_rotation, this is the rule to start with:
get_sector_rotation is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crypto Intelligence, apply this rule, and every get_sector_rotation call is checked against it from then on.
Questions about get_sector_rotation
Cross-sectional rotation metrics across core (32 coins) or all-universe cohort. $0.10. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for get_sector_rotation: 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 Crypto Intelligence. Nothing to install.
get_sector_rotation 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_sector_rotation 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_sector_rotation. 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_sector_rotation is provided by the Crypto Intelligence MCP server (https://api.carbon-cashmere.de/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto Intelligence, and thousands of servers like it.
This server
Across the catalogue