report_mcpize_link
Check MCPize subscription status for a DataNexus tool. tool_id: DataNexus tool identifier e.g. "T10". Pass the tool the user is asking about. Returns: status ("free" | "subscription_required" | "not_configured"), message, tool_id, and upgrade_url when subscription is required. Example: report_mcp...
This record as markdown: /tools/dev-7bd0-mcp-server/report-mcpize-link.md
What report_mcpize_link does on DataNexus MCP
AI agents call report_mcpize_link to retrieve information from DataNexus MCP 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 |
|---|---|---|---|
tool_id | string | — | DataNexus tool identifier to check, e.g. "T01", "T07", "T10" — pass the ID of the tool the user is asking about. |
Parameters from the server's own tool schema.
Why report_mcpize_link is rated Low
This tool performs a read-only query of subscription status information for a DataNexus tool. It retrieves and returns status data ('free', 'subscription_required', 'not_configured') along with metadata (message, tool_id, upgrade_url). There are no side effects, no data modification, no code execution, and no destructive operations.
From the tool's definition Tool description states it 'Check[s] MCPize subscription status' and 'Returns: status...message, tool_id, and upgrade_url'. The operation retrieves subscription metadata without modifying any data or triggering external actions.
Attacks that exploit this kind of access
The rule that runs report_mcpize_link safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For report_mcpize_link, this is the rule to start with:
report_mcpize_link 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 DataNexus MCP, apply this rule, and every report_mcpize_link call is checked against it from then on.
Questions about report_mcpize_link
Check MCPize subscription status for a DataNexus tool. tool_id: DataNexus tool identifier e.g. "T10". Pass the tool the user is asking about. Returns: status ("free" | "subscription_required" | "not_configured"), message, tool_id, and upgrade_url when subscription is required. Example: report_mcpize_link(tool_id="T10"). It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
report_mcpize_link accepts 1 parameter: tool_id. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for report_mcpize_link: 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 DataNexus MCP. Nothing to install.
report_mcpize_link 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 report_mcpize_link 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 report_mcpize_link. 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.
report_mcpize_link is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue