AI agents call sch_get to retrieve information from TOOL4LM without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is a Read operation—it retrieves scholarly research data without side effects. No modification, deletion, execution, or financial impact is indicated. Severity is low because information retrieval from scholarly sources poses minimal risk of harm if misused by an AI agent, though the confidence is slightly moderated (0.85) due to the alias indirection and lack of explicit operation description.
From the tool's definition Tool 'sch_get' is described as an alias of 'sch.get', which based on the sibling tool naming convention (alongside sch_search) appears to be a scholarly research retrieval tool.
Attacks that exploit this kind of access
Alias of sch.get. It is categorised as a Read tool in the TOOL4LM MCP Server, which means it retrieves data without modifying state.
Register the TOOL4LM MCP server in PolicyLayer and add a rule for sch_get: 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 TOOL4LM. Nothing to install.
sch_get 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 sch_get 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 sch_get. 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.
sch_get is provided by the TOOL4LM MCP server (khanhs-234/tool4lm). 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 →