AI agents call get_recipe_by_index to retrieve information from MatMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple lookup operation on existing recipe data. There is no modification, deletion, or execution involved. The worst-case misuse scenario is retrieving unintended recipe information, which has minimal security impact. Classified as Read with low severity.
From the tool's definition Tool description states 'Get a recipe by index from the list' — a retrieval operation with no side effects. It queries and returns recipe data without modifying, deleting, or executing any external operations.
Attacks that exploit this kind of access
Get a recipe by index from the list. It is categorised as a Read tool in the MatMCP MCP Server, which means it retrieves data without modifying state.
Register the Mat MCP server in PolicyLayer and add a rule for get_recipe_by_index: 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 MatMCP. Nothing to install.
get_recipe_by_index 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_recipe_by_index 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_recipe_by_index. 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_recipe_by_index is provided by the Mat MCP server (sleipner42/mathem-mcp-server). 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 →