# search_stock_images A read tool on the Postking Mcp MCP server. Agent View of the PolicyLayer registry record for `search_stock_images`. HTML page: https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/search-stock-images ## Facts - Tool: `search_stock_images` - Server: Postking Mcp (`postking-mcp`) — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp.md - Install: `npx -y postking-mcp` - Homepage: https://github.com/bitsandtea/postking-mcp - Risk category: Read (Low risk) - Registry record: grade D, identity unverified - Server auth posture: gated - Server CORS policy: * - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "search_stock_images", "arguments": {} } } ``` ## Why search_stock_images is rated Low Searching stock images is a read-only operation with no side effects—it retrieves data for selection without creating, modifying, or destroying anything. The empty description prevents higher confidence, but the name is sufficiently explicit. In the context of a content management server (PostKing), this is a safe retrieval tool for browsing available images. From the tool's own definition: "Tool name 'search_stock_images' indicates a search operation that retrieves data without modifying or deleting anything. Description is empty, which limits confidence, but the name clearly suggests querying a stock image database." ## Use case AI agents call search_stock_images to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Postking Mcp: ```json { "version": "1", "default": "deny", "tools": { "search_stock_images": {} } } ``` ## Other tools on Postking Mcp (224) - `brand_truth_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/brand-truth-delete.md - `cancel_job` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/cancel-job.md - `competitor_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/competitor-delete.md - `delete_asset` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-asset.md - `delete_blog_article` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-blog-article.md - `delete_domain` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-domain.md - `delete_landing_page` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-landing-page.md - `delete_lp_version` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-lp-version.md - `delete_post` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-post.md - `delete_side_page` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-side-page.md - `delete_theme` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-theme.md - `delete_weekly_schedule` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-weekly-schedule.md - `knowledge_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/knowledge-delete.md - `logout` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/logout.md - `revoke_api_key` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/revoke-api-key.md - `seo_delete_keyword` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/seo-delete-keyword.md - `seo_roadmap_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/seo-roadmap-delete.md - `storyline_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-delete.md - `storyline_delete_line_item` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-delete-line-item.md - `template_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/template-delete.md - `competitor_refresh` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/competitor-refresh.md - `generate_connect_link` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/generate-connect-link.md - `generate_text` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/generate-text.md - `generate_themes` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/generate-themes.md - `run_weekly_schedule_day` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/run-weekly-schedule-day.md - `seo_generate_clusters` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/seo-generate-clusters.md - `storyline_execute` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-execute.md - `storyline_regenerate_line_item` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-regenerate-line-item.md - `billing_subscribe` — Financial — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/billing-subscribe.md - `billing_topup` — Financial — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/billing-topup.md - …and 194 more: https://policylayer.com/tools/io-github-bitsandtea-postking-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-bitsandtea-postking-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-bitsandtea-postking-mcp