タイトル、説明、URL、タグでアイテムを検索します。スペースで区切られた複数のキーワードをOR検索します
AI agents call jser_search_items to retrieve information from JSer Info MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches existing JavaScript resource data from a database. It performs read-only operations: searching by title, description, URL, and tags. There are no side effects, no data modification, no code execution, and no destructive operations. This is consistent with standard search functionality that only queries and returns results.
From the tool's definition Tool name 'jser_search_items' and description 'タイトル、説明、URL、タグでアイテムを検索します。スペースで区切られた複数のキーワードをOR検索します' (Searches items by title, description, URL, tags with space-separated keywords using OR search) indicate a search/query operation with no data modification or…
Documented attack patterns abuse exactly the kind of access jser_search_items gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JSer Info MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for jser_search_items:
{
"version": "1",
"default": "deny",
"tools": {
"jser_search_items": {}
}
} jser_search_items 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.
タイトル、説明、URL、タグでアイテムを検索します。スペースで区切られた複数のキーワードをOR検索します. It is categorised as a Read tool in the JSer Info MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JSer Info MCP Server MCP server in PolicyLayer and add a rule for jser_search_items: 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 JSer Info MCP Server. Nothing to install.
jser_search_items 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 jser_search_items 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 jser_search_items. 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.
jser_search_items is provided by the JSer Info MCP Server MCP server (jser/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JSer Info MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 JSer Info MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.