search_professors
AI agents call search_professors to retrieve information from Professor Fit MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to search or retrieve professor information for matching purposes. No description suggests data modification, deletion, or external operations. The lack of explicit destructive keywords and the server's read-focused purpose (searching, ranking, outputting tables) indicate a Read classification.
From the tool's definition Tool is called 'search_professors' with an empty description, but exists alongside 'find_professors' and 'rank_fit' in a server that 'helps PhD applicants find matching professors.' Given the server's purpose and sibling tools that explicitly find and rank…
Attacks that exploit this kind of access
search_professors. It is categorised as a Read tool in the Professor Fit MCP MCP Server, which means it retrieves data without modifying state.
Register the Professor Fit MCP server in PolicyLayer and add a rule for search_professors: 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 Professor Fit MCP. Nothing to install.
search_professors 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 search_professors 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 search_professors. 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.
search_professors is provided by the Professor Fit MCP server (wrennnn2/professorfitmcp). 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 →