explain_peaks
AI agents call explain_peaks to retrieve information from FTIR Fun MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to accept peak list data and return explanatory information about those peaks, consistent with a read-only analytical operation. The empty description reduces confidence slightly, but the context of FTIR spectrum analysis and the pattern of sibling tools (which are queries and fetches) indicates this is a retrieval/analysis tool with no side effects that could damage data or systems.
From the tool's definition Tool name 'explain_peaks' and sibling tools 'analyze_ftir_spectrum', 'fetch_result', 'find_spectra' all perform spectral analysis and data retrieval without modification.
Attacks that exploit this kind of access
explain_peaks. It is categorised as a Read tool in the FTIR Fun MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FTIR Fun MCP Server MCP server in PolicyLayer and add a rule for explain_peaks: 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 FTIR Fun MCP Server. Nothing to install.
explain_peaks 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 explain_peaks 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 explain_peaks. 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.
explain_peaks is provided by the FTIR Fun MCP Server MCP server (jxbaoxiaodong/ftirfun-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 →