Return the full vendor fact sheet (per GTM Decision Schema v1.0.0) for a tool, when one exists. Includes pricing tiers with gotchas, integration depth scores, AI capabilities + customer-data-for-training disclosure, affiliate program terms, and self-disclosed conflicts (vendor-claim vs user-repor...
AI agents call get_vendor_fact_sheet to retrieve information from StackSwap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tool | string | Yes | Tool name or slug (e.g. "Apollo.io", "apollo", "Smartlead"). Fuzzy-matched against the catalog. |
Parameters from the server's own tool schema.
This is a pure data retrieval tool that queries and presents existing vendor information in a machine-readable format. The worst-case misuse by an AI agent is retrieving sensitive vendor details or making poor purchasing decisions based on the data—typical read-only risks with low blast radius. No side effects, no irreversible actions, no code execution, no financial transactions.
From the tool's definition Tool returns structured vendor fact sheet data (pricing, integrations, AI capabilities, affiliate terms, conflicts).
Attacks that exploit this kind of access
Return the full vendor fact sheet (per GTM Decision Schema v1.0.0) for a tool, when one exists. Includes pricing tiers with gotchas, integration depth scores, AI capabilities + customer-data-for-training disclosure, affiliate program terms, and self-disclosed conflicts (vendor-claim vs user-reported). Provenance is labeled (vendor / stackswap / community) and freshness is computed against a 90-day window. Use when an agent or buyer needs the structured machine-readable view of a tool — strictly more detail than get_tool_details. Returns a not-found message + a pointer to /vendors/submit-fact-sheet when no fact sheet exists. It is categorised as a Read tool in the StackSwap MCP Server, which means it retrieves data without modifying state.
get_vendor_fact_sheet accepts 1 parameter: tool. Required: tool. The full parameter table on this page comes from the server's own tool schema.
Register the StackSwap MCP server in PolicyLayer and add a rule for get_vendor_fact_sheet: 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 StackSwap. Nothing to install.
get_vendor_fact_sheet 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 get_vendor_fact_sheet 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 get_vendor_fact_sheet. 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.
get_vendor_fact_sheet is provided by the StackSwap MCP server (StonesofCreation/stackswap-mcp). 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 →