メンバーを検索
AI agents call search_members to retrieve information from Ghost 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 or queries member data from the Ghost CMS without creating, modifying, or deleting any records. It has no side effects on the system state. While member data may be considered sensitive (personal information), the read-only nature keeps this in the Read category. The blast radius of misuse is limited to unauthorized data access rather than data loss or system compromise.
From the tool's definition Tool name 'search_members' and description indicate a search/query operation. The verb 'search' combined with the Ghost API context (querying members data) denotes a read-only retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
メンバーを検索. It is categorised as a Read tool in the Ghost MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ghost MCP Server MCP server in PolicyLayer and add a rule for search_members: 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 Ghost MCP Server. Nothing to install.
search_members 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_members 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_members. 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_members is provided by the Ghost MCP Server MCP server (mtane0412/ghost-mcp-server). 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 →