Skip to content

FUTURE_CONSIDERATIONS.md

Latest commit

 

History

History
64 lines (42 loc) · 3.1 KB

FUTURE_CONSIDERATIONS.md

File metadata and controls

64 lines (42 loc) · 3.1 KB
Raw

Future Considerations

This document records possible areas for future versions of the Agent Plugins Specification. It is non-normative, and none of these items is required for conformance or committed for inclusion in a future release.

Permission and approval UX

v1.0.0 does not define a trust model, permission system, or sandboxing requirements for plugins. A future version should address:

  • Permission declarations in the manifest (e.g., filesystem access, network access, tool access)
  • Client-enforced capability restrictions per plugin
  • User consent flows for plugin installation and capability grants
  • Approval UX for MCP servers that execute arbitrary commands or access external services
  • Graduated trust levels (e.g., "sandboxed", "user-approved", "organization-approved")

Provenance verification

v1.0.0 does not specify how clients or users can verify the origin or integrity of a plugin. A future version may define:

  • Cryptographic signature verification for published plugins
  • Attestation chains linking a published plugin to its source repository and build
  • Client policies for requiring signatures from trusted publishers

Secret and sensitive value handling

MCP servers often need credentials or API keys at runtime. v1.0.0 does not specify how sensitive values should be provided, stored, or scoped. A future version may define:

  • A secrets manifest field or separate secrets configuration
  • Client-mediated secret injection that avoids plaintext in config files
  • Scoping rules that prevent one plugin from accessing another plugin's secrets
  • Rotation and revocation semantics for plugin-held credentials

Enterprise controls

Organizations deploying plugins at scale need policy enforcement that v1.0.0 does not address. A future version may define:

  • Allowlist and blocklist policies for plugin installation by name, publisher, or signature
  • Organization-scoped plugin registries with approval workflows
  • Centralized configuration overrides that take precedence over user-level plugin settings
  • Compliance reporting for plugin installation and usage events

Audit-trail standardization

v1.0.0 defines failure-reporting requirements but does not standardize diagnostic or lifecycle event schemas. A future version may define:

  • A standard event schema for plugin install, enable, disable, update, and uninstall actions
  • Recommended fields: timestamp, actor (user or automation), plugin name, plugin version, action, outcome
  • Integration points for forwarding audit events to external logging or SIEM systems
  • Retention and access policies for audit records

Dependency resolution

Plugins currently cannot declare dependencies on other plugins. A future version may define:

  • A dependencies manifest field with version constraints
  • Resolution order and conflict handling for transitive dependencies
  • Peer dependency semantics for shared components

Plugin testing and validation

No test harness or validation tool is specified. A future version may define:

  • A test manifest field or convention
  • A standard plugin linter or validator command
  • Conformance test suites for client implementations