AI agents call search_user to retrieve information from PTT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A user search function on a bulletin board system is expected to retrieve user profile or account information without modifying data. No write, execute, destructive, or financial operations are implied by the name. The confidence is slightly reduced due to the missing description, but the naming convention and server context support a Read classification as the most reasonable interpretation.
From the tool's definition Tool name 'search_user' indicates a query operation that retrieves user information. The empty description limits direct evidence, but the name pattern and server context (PTT bulletin board system) strongly suggest a read-only lookup function.
Documented attack patterns abuse exactly the kind of access search_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PTT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_user:
{
"version": "1",
"default": "deny",
"tools": {
"search_user": {}
}
}search_user is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_user. It is categorised as a Read tool in the PTT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PTT MCP Server MCP server in PolicyLayer and add a rule for search_user: 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 PTT MCP Server. Nothing to install.
search_user 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_user 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_user. 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_user is provided by the PTT MCP Server MCP server (pyptt/ptt_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 PTT MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 PTT MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.