AI agents call jser_search_posts 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 queries existing data from the JSer.info database without creating, modifying, or deleting records. It is a straightforward search function analogous to a database SELECT query, placing it in the Read category with low severity and high confidence.
From the tool's definition Tool description indicates 'search' functionality for posts by title, description, URL, and tags. The name 'jser_search_posts' and description (「投稿を検索します」= search posts) clearly denote a retrieval/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access jser_search_posts 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_posts:
{
"version": "1",
"default": "deny",
"tools": {
"jser_search_posts": {}
}
}jser_search_posts 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、タグで投稿を検索します. 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_posts: 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_posts 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_posts 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_posts. 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_posts 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.