Get content for all core rules in the index. Returns a list of strings.
AI agents call GetCoreRulesContent to retrieve information from ContextualAgentRulesHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries rule content data without any side effects. It is a straightforward read operation that fetches information from an index. The low severity reflects minimal blast radius—misuse would only result in unauthorized access to stored rules/guidelines, not destructive or operational consequences.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get content for all core rules' and 'Returns a list of strings.' No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
Get content for all core rules in the index. Returns a list of strings. It is categorised as a Read tool in the ContextualAgentRulesHub MCP Server, which means it retrieves data without modifying state.
Register the ContextualAgentRulesHub MCP server in PolicyLayer and add a rule for GetCoreRulesContent: 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 ContextualAgentRulesHub. Nothing to install.
GetCoreRulesContent 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 GetCoreRulesContent 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 GetCoreRulesContent. 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.
GetCoreRulesContent is provided by the ContextualAgentRulesHub MCP server (oshvartz/contextualagentruleshub). 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 →