security_fetch_package_maintainer_history
Analyse ownership and release history for an npm or PyPI package to detect supply-chain risk. Uses PyPI JSON API and npm registry — data refreshed on each call, 1-hour cache. Returns maintainer_count, recent_changes, ownership_transfers, account_ages, anomaly_score (0.0–1.0), and maintainer_healt...
This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-package-maintainer-history.md
What security_fetch_package_maintainer_history does on DataNexus MCP
AI agents call security_fetch_package_maintainer_history 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 |
|---|---|---|---|
ecosystem | string | — | Package ecosystem: npm, pypi, cargo, go. Required. |
package_name | string | — | Package name e.g. requests. Required. |
Parameters from the server's own tool schema.
Why security_fetch_package_maintainer_history is rated Low
This tool queries existing public registry data to surface supply-chain risk signals, with no ability to modify packages, trigger deployments, execute code, delete records, or move funds. The analysis is performed on retrieved data, not the tool itself executing arbitrary operations. This is a classic Read pattern: retrieval + structured inspection of immutable public sources for security intelligence.
From the tool's definition Tool 'retrieves' and 'analyzes' package maintainer history from public npm/PyPI registries; returns data fields like maintainer_count, recent_changes, ownership_transfers, account_ages, anomaly_score, and maintainer_health.
Attacks that exploit this kind of access
The rule that runs security_fetch_package_maintainer_history 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 security_fetch_package_maintainer_history, this is the rule to start with:
security_fetch_package_maintainer_history 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 security_fetch_package_maintainer_history call is checked against it from then on.
Questions about security_fetch_package_maintainer_history
Analyse ownership and release history for an npm or PyPI package to detect supply-chain risk. Uses PyPI JSON API and npm registry — data refreshed on each call, 1-hour cache. Returns maintainer_count, recent_changes, ownership_transfers, account_ages, anomaly_score (0.0–1.0), and maintainer_health (healthy | stale | abandoned | suspicious). Rate limit: 60/minute. No auth required. For security engineers auditing open-source dependencies before inclusion in production builds. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_package_maintainer_history", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
security_fetch_package_maintainer_history accepts 2 parameters: ecosystem, package_name. 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 security_fetch_package_maintainer_history: 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.
security_fetch_package_maintainer_history 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 security_fetch_package_maintainer_history 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 security_fetch_package_maintainer_history. 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.
security_fetch_package_maintainer_history 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