AI agents call list_conventions to retrieve information from Shikamaru without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward information retrieval operation. It queries and returns a static or semi-static list of supported day-count conventions (ISDA/ICMA standards). There are no side effects, no data modification, no code execution, and no irreversible actions. This is a classic Read category tool with minimal security risk.
From the tool's definition Tool name 'list_conventions' and description 'List the supported day-count conventions' indicates a query operation that retrieves and returns information about available conventions without modifying any data or triggering external operations.
Attacks that exploit this kind of access
List the supported day-count conventions. It is categorised as a Read tool in the Shikamaru MCP Server, which means it retrieves data without modifying state.
Register the Shikamaru MCP server in PolicyLayer and add a rule for list_conventions: 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 Shikamaru. Nothing to install.
list_conventions 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 list_conventions 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 list_conventions. 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.
list_conventions is provided by the Shikamaru MCP server (JayOfemi/shikamaru). 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 →