company_profile
Company profile from its own website: name, description, logo, social profiles, contact emails/phones, postal address, schema.org Organization JSON-LD, OpenGraph/Twitter cards, plus RDAP domain registration basics (registered, expires, registrar). SSRF-safe fetch of the public page. Price: $0.03 ...
This record as markdown: /tools/com-it-scorptech-x402/company-profile.md
What company_profile does on ScorpTech x402 API
AI agents call company_profile to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Company website URL or bare domain (public http(s) only) |
Parameters from the server's own tool schema.
Why company_profile is rated Low
Even though company_profile only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs company_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For company_profile, this is the rule to start with:
company_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every company_profile call is checked against it from then on.
Questions about company_profile
Company profile from its own website: name, description, logo, social profiles, contact emails/phones, postal address, schema.org Organization JSON-LD, OpenGraph/Twitter cards, plus RDAP domain registration basics (registered, expires, registrar). SSRF-safe fetch of the public page. Price: $0.03 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/company-profile. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
company_profile accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for company_profile: 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 ScorpTech x402 API. Nothing to install.
company_profile 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 company_profile 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 company_profile. 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.
company_profile is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue